| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 6 Aug 2014 11:59:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Mark Rutland <mark.rutland@....com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] regulator: userspace-consumer: add DT binding details
On Wed, Aug 06, 2014 at 01:03:52PM +0530, Laxman Dewangan wrote:
> On Wednesday 30 July 2014 10:10 PM, Mark Brown wrote:
> >Yes, this is test code - it is not intended to be used in production.
> >Any binding should be for the consumer using this, not for this
> >implementation detail.
> We have the GPS module and its driver in the user space. There is no code
> for GPS on kernel. Just power on and open port from user space, get the
> information.
That's an implementation detail of how you've provided this on Linux.
> On this case, how do we power on GPS module if we don't expose it? It need
> two power source for digital section and analog section.
Describe the hardware in the device tree and then bind what's needed to
that.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists