From: Mark Brown <broonie@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Pawel Moll <Pawel.Moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] regulator: userspace-consumer: add DT binding details
Date: Wed, 6 Aug 2014 11:59:15 +0100 [thread overview]
Message-ID: <20140806105915.GH17528@sirena.org.uk> (raw)
In-Reply-To: <53E1DA60.9010401@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-06 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:53 [PATCH 2/2] regulator: userspace-consumer: add DT support Laxman Dewangan
2014-07-30 13:53 ` Laxman Dewangan
2014-07-30 13:54 ` [PATCH 1/2] regulator: userspace-consumer: add DT binding details Laxman Dewangan
2014-07-30 13:54 ` Laxman Dewangan
2014-07-30 15:53 ` Mark Rutland
2014-07-30 15:53 ` Mark Rutland
2014-07-30 16:40 ` Mark Brown
2014-07-30 16:40 ` Mark Brown
2014-08-06 7:33 ` Laxman Dewangan
2014-08-06 10:59 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140806105915.GH17528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.