From: Johan Hovold <johan@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Johan Hovold <johan@kernel.org>,
bcousson@baylibre.com, tony@atomide.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
letux-kernel@openphoenux.org
Subject: Re: [PATCH] arm: dts: gta04: add gps support
Date: Wed, 30 Jan 2019 10:02:32 +0100 [thread overview]
Message-ID: <20190130090232.GL3691@localhost> (raw)
In-Reply-To: <20190128163025.7daa385b@kemnade.info>
On Mon, Jan 28, 2019 at 05:44:29PM +0100, Andreas Kemnade wrote:
> On Mon, 28 Jan 2019 08:53:56 +0100
> Johan Hovold <johan@kernel.org> wrote:
>
> > On Fri, Jan 25, 2019 at 08:43:10PM +0100, Andreas Kemnade wrote:
> > > The GTA04 has a w2sg0004 or w2sg0084 gps chip. Not detectable
> > > which one is mounted so use the compatibility entry for w2sg0004
> > > for all which will work for both.
> > >
> > > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > > ---
> > > w2sg0004 bindings (together with the corresponding support is in
> > > https://git.kernel.org/pub/scm/linux/kernel/git/johan/gnss gnss-next)
> > > arch/arm/boot/dts/omap3-gta04.dtsi | 13 +++++++++++++
> > > 1 file changed, 13 insertions(+)
> > > + gps: gps {
> >
> > The node should be named "gnss" as per the binding.
> >
> > > + compatible = "wi2wi,w2sg0004";
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&gps_pins>;
> > > + sirf,onoff-gpios = <&gpio5 17 GPIO_ACTIVE_HIGH>;
> > > + lna-supply = <&vsim>;
> >
> > Also, the vcc-supply is a required property.
> >
> well, it is not require in the driver and it has different behavior
> (on even when not opened if on-off is there) than the lna-supply used
> here. So maybe fix the binding documentation?
The device-tree describes hardware, and how a particular driver happens
to implement a binding is not relevant.
That said, there is a bit of an on-going, shall we say philosophical,
debate about this. The regulator maintainer takes a firm position that
all mandatory physical supplies should be represented in firmware
https://lore.kernel.org/lkml/20181123133126.GF2089@sirena.org.uk/T/#u
https://lore.kernel.org/lkml/20180409102244.GB11532@sirena.org.uk/T/#u
while Rob appears to take a slightly different stance on fixed
regulators while admitting that this an issue which has not yet been
fully resolved:
https://lore.kernel.org/lkml/20180425171123.xhyoay3nu463btoq@rob-hp-laptop/T/#u
Since this is a new binding, and the hardware requires the vcc supply
and this is reflected in the binding, I think you should add a fixed
regulator. At least until you hear otherwise. ;)
Johan
next prev parent reply other threads:[~2019-01-30 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 19:43 [PATCH] arm: dts: gta04: add gps support Andreas Kemnade
2019-01-28 7:53 ` Johan Hovold
2019-01-28 16:44 ` Andreas Kemnade
2019-01-30 9:02 ` Johan Hovold [this message]
2019-01-30 14:06 ` [Letux-kernel] " H. Nikolaus Schaller
2019-01-30 20:11 ` Andreas Kemnade
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=20190130090232.GL3691@localhost \
--to=johan@kernel.org \
--cc=andreas@kemnade.info \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).