From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver Date: Mon, 12 Feb 2018 16:26:18 +0100 Message-ID: <20180212152618.GC13962@amd> References: <5494ad34b39a6c62601e3747440268dfb3be7d5a.1512114576.git.hns@goldelico.com> <20171222124427.GI3374@localhost> <91850CC3-B280-4701-9D07-96AFF3A79A6F@goldelico.com> <90F9A8E4-035A-4A9E-8AAB-757491D63E69@goldelico.com> <20180112153903.GB5992@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dkEUBIird37B8yKS" Return-path: Content-Disposition: inline In-Reply-To: <20180112153903.GB5992@localhost> Sender: linux-kernel-owner@vger.kernel.org To: Johan Hovold Cc: "H. Nikolaus Schaller" , Mark Rutland , DTML , Thierry Reding , Jonathan Cameron , Arnd Bergmann , Tony Lindgren , Greg Kroah-Hartman , Russell King , Linux Kernel Mailing List , Rob Herring , Kevin Hilman , =?iso-8859-1?Q?Beno=EEt?= Cousson , kernel@pyra-handheld.com, Discussions about the Letux Kernel , linux-omap , Andreas =?iso-8859-1?Q?F=E4rber?= , Linux ARM List-Id: devicetree@vger.kernel.org --dkEUBIird37B8yKS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > Let's restart this discussion and focus on the main roadblock (others > > are minor details which can be sorted out later). > >=20 > > If it feels like a hack, the key issue seems to me to be the choice of > > the API to present the GPS data to user space. Right? >=20 > Or even more fundamentally, does this belong in the kernel at all? Yes, it does. > Given that we'd still depend on gpsd and other, proprietary, daemons to > actually parse and use (also for control) the plethora of GPS protocols > available, it may even be best to just keep it all in user space. No. We'd want to move away from gpsd in the long term. (/dev/input/mice was in similar situation.) > Now, if we'd ever have a proper GPS framework that handled everything in > kernel space (i.e. no more gpsd) then we would be able to write kernel > drivers that also take care of PM. But perhaps that's unlikely to ever > be realised given the state of things (proprietary protocols, numerous > quirky implementations, etc). That is what needs to happen. > The kernel is probably not the place to be working around issues like > that, even if serdev at least allows for such hacks to be fairly > isolated in drivers (unlike some of the earlier proposals touching core > code). Oh, kernel is indeed right place to provide hardware abstraction -- and that includes bug workarounds. We'd like unmodified userspace to run on any supported hardware, remember? Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --dkEUBIird37B8yKS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlqBshoACgkQMOfwapXb+vLq0ACfa+0cUfIudCx3JKPfpMHeQ9Fk se8AoIjq1ci/aJ0lgBOdyzieOOILfG/Q =amcf -----END PGP SIGNATURE----- --dkEUBIird37B8yKS--