[Letux-kernel] [PATCH 0/7] gnss: add new GNSS subsystem
johan at kernel.org
Wed Apr 25 10:11:20 CEST 2018
On Tue, Apr 24, 2018 at 09:44:08PM +0200, H. Nikolaus Schaller wrote:
> > Am 24.04.2018 um 19:50 schrieb Johan Hovold <johan at kernel.org>:
> > I think it should be done the other way round (if I understand you
> > correctly), that is, by adding support for configurations were WAKEUP is
> > left not connected to the sirf driver instead.
> Hm. Yes, the w2sg00x4 is a Sirf based chip.
> > I had that use-case in mind when implementing
> > the driver, and some ideas of how it should be
> > done, but did not get around to actually implement it yet.
> What do you need ideas for? We have that function working and
> submitted year after year, but it was always rejected for API
> You could have simply reused what we have proposed  and just
> adapt it to the new API instead of writing a new driver (which
> is missing some features for us).
Your code was broken or needed to be updated in several ways as I
pointed out in the thread you refer to.
It also did not support all those systems that use the same family of
chips, but which has the WAKEUP signal connected.
> "proof-of-concept" is misleading if you expect this to become
> *the* Sirf driver and we are just invited to add some features
> to that. Making our own work and proposals completely obsolete.
> What I find really strange and foul play is that we are in the
> review process and then comes a hidden counter-proposal by the
Dude, in the very same thread you refer to above, after being asked to
reiterate your proposal to find and appropriate abstraction level you
"Yes, please feel free to write patches that implement it that
Now I've done just that for you, and then you whine about that too.
SiRF is a very common chip and I wanted to make sure that the common
setup with WAKEUP connected was supported from the start. I'll get to
your configuration in time too.
> : https://patchwork.ozlabs.org/cover/843392/
More information about the Letux-kernel