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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 6 Aug 2014 13:03:52 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Mark Brown <broonie@...nel.org>,
	Mark Rutland <mark.rutland@....com>
CC:	"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 Wednesday 30 July 2014 10:10 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jul 30, 2014 at 04:53:03PM +0100, Mark Rutland wrote:
>> On Wed, Jul 30, 2014 at 02:54:00PM +0100, Laxman Dewangan wrote:
>>> +Required properties:
>>> +- compatible		: Must be "reg-userspace-consumer".
>> I would never expect to see "userspace" in a DT beinding string; this is
>> entirely a software abstraction description and has nothing to do with
>> the interaction of HW components.
>> Why do you think we need this in the DT?
> 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.

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ