| Message ID | 20190131180640.14480-3-andreas@kemnade.info (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | arm: dts: gta04: add gps support | expand |
On Thu, Jan 31, 2019 at 07:06:40PM +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> > --- > Changes in v3: > - converted to a patchset > - added vcc-supply > > Changes in v2: > - some s/gps/gnss/ > - not added vcc-supply because the regulator is not modelled > in dts at all > > w2sg0004 bindings are in next-20190129 > > arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi > index 02d8274a2f47..4ea0f7dc37c6 100644 > --- a/arch/arm/boot/dts/omap3-gta04.dtsi > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi > @@ -320,6 +320,12 @@ > >; > }; > > + gps_pins: pinmux_gps_pins { s/gps/gnss/ would be more consistent, but whatever. > + pinctrl-single,pins = < > + OMAP3_CORE1_IOPAD(0x2176, PIN_OUTPUT_PULLDOWN | MUX_MODE4) /* gpio145 */ > + >; > + }; > + > hdq_pins: hdq_pins { > pinctrl-single,pins = < > OMAP3_CORE1_IOPAD(0x21c6, PIN_INPUT_PULLUP | MUX_MODE0) /* i2c3_sda.hdq */ > @@ -652,6 +658,14 @@ > &uart2 { > pinctrl-names = "default"; > pinctrl-0 = <&uart2_pins>; > + gnss: gnss { > + compatible = "wi2wi,w2sg0004"; > + pinctrl-names = "default"; > + pinctrl-0 = <&gps_pins>; > + sirf,onoff-gpios = <&gpio5 17 GPIO_ACTIVE_HIGH>; > + lna-supply = <&vsim>; > + vcc-supply = <&ldo_3v3>; > + }; Reviewed-by: Johan Hovold <johan@kernel.org> Johan
On Fri, 1 Feb 2019 11:04:16 +0100 Johan Hovold <johan@kernel.org> wrote: > On Thu, Jan 31, 2019 at 07:06:40PM +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> > > --- > > Changes in v3: > > - converted to a patchset > > - added vcc-supply > > > > Changes in v2: > > - some s/gps/gnss/ > > - not added vcc-supply because the regulator is not modelled > > in dts at all > > > > w2sg0004 bindings are in next-20190129 > > > > arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ > > 1 file changed, 14 insertions(+) > > > > diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi > > index 02d8274a2f47..4ea0f7dc37c6 100644 > > --- a/arch/arm/boot/dts/omap3-gta04.dtsi > > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi > > @@ -320,6 +320,12 @@ > > >; > > }; > > > > + gps_pins: pinmux_gps_pins { > > s/gps/gnss/ would be more consistent, but whatever. > well, gps is already in the file at another place. So it is a bit inconsistent in any case, without further cleanup. If someone comes up with a strong opinion here I would of course change it. Regards, Andreas
Hi Andreas, > Am 01.02.2019 um 20:06 schrieb Andreas Kemnade <andreas@kemnade.info>: > > On Fri, 1 Feb 2019 11:04:16 +0100 > Johan Hovold <johan@kernel.org> wrote: > >> On Thu, Jan 31, 2019 at 07:06:40PM +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> >>> --- >>> Changes in v3: >>> - converted to a patchset >>> - added vcc-supply >>> >>> Changes in v2: >>> - some s/gps/gnss/ >>> - not added vcc-supply because the regulator is not modelled >>> in dts at all >>> >>> w2sg0004 bindings are in next-20190129 >>> >>> arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ >>> 1 file changed, 14 insertions(+) >>> >>> diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi >>> index 02d8274a2f47..4ea0f7dc37c6 100644 >>> --- a/arch/arm/boot/dts/omap3-gta04.dtsi >>> +++ b/arch/arm/boot/dts/omap3-gta04.dtsi >>> @@ -320,6 +320,12 @@ >>> >; >>> }; >>> >>> + gps_pins: pinmux_gps_pins { >> >> s/gps/gnss/ would be more consistent, but whatever. >> > well, gps is already in the file at another place. So it is a bit > inconsistent in any case, without further cleanup. If someone comes > up with a strong opinion here I would of course change it. For me the highest priority is that it works. And that does not depend on the specific node name. The pinmux node is only referenced through a phandle, which is translated into a pure numeric code by DTC. Another argument could be that the w2sg0004 chip was introduced ca. 2007 when GPS was (AFAIR) the only GNSS system widely available and the only one supported by the chip. So this would be an argument for "gps" since it is a "GPS only" receiver chip. Since the DT should describe specific hardware, it maybe should somehow codify that the chip is GPS only and is not a generic gnss chip (although the driver knows that as well). BR, Nikolaus
On Fri, Feb 01, 2019 at 08:06:30PM +0100, Andreas Kemnade wrote: > On Fri, 1 Feb 2019 11:04:16 +0100 > Johan Hovold <johan@kernel.org> wrote: > > > On Thu, Jan 31, 2019 at 07:06:40PM +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> > > > --- > > > Changes in v3: > > > - converted to a patchset > > > - added vcc-supply > > > > > > Changes in v2: > > > - some s/gps/gnss/ > > > - not added vcc-supply because the regulator is not modelled > > > in dts at all > > > > > > w2sg0004 bindings are in next-20190129 > > > > > > arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ > > > 1 file changed, 14 insertions(+) > > > > > > diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi > > > index 02d8274a2f47..4ea0f7dc37c6 100644 > > > --- a/arch/arm/boot/dts/omap3-gta04.dtsi > > > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi > > > @@ -320,6 +320,12 @@ > > > >; > > > }; > > > > > > + gps_pins: pinmux_gps_pins { > > > > s/gps/gnss/ would be more consistent, but whatever. > > > well, gps is already in the file at another place. So it is a bit > inconsistent in any case, without further cleanup. If someone comes > up with a strong opinion here I would of course change it. Up to you. As long as the gnss node is named "gnss" I don't have a strong opinion on the other names (as long as they follow the spec of course). Johan
* Johan Hovold <johan@kernel.org> [190204 08:30]: > On Fri, Feb 01, 2019 at 08:06:30PM +0100, Andreas Kemnade wrote: > > On Fri, 1 Feb 2019 11:04:16 +0100 > > Johan Hovold <johan@kernel.org> wrote: > > > > > On Thu, Jan 31, 2019 at 07:06:40PM +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> > > > > --- > > > > Changes in v3: > > > > - converted to a patchset > > > > - added vcc-supply > > > > > > > > Changes in v2: > > > > - some s/gps/gnss/ > > > > - not added vcc-supply because the regulator is not modelled > > > > in dts at all > > > > > > > > w2sg0004 bindings are in next-20190129 > > > > > > > > arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ > > > > 1 file changed, 14 insertions(+) > > > > > > > > diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi > > > > index 02d8274a2f47..4ea0f7dc37c6 100644 > > > > --- a/arch/arm/boot/dts/omap3-gta04.dtsi > > > > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi > > > > @@ -320,6 +320,12 @@ > > > > >; > > > > }; > > > > > > > > + gps_pins: pinmux_gps_pins { > > > > > > s/gps/gnss/ would be more consistent, but whatever. > > > > > well, gps is already in the file at another place. So it is a bit > > inconsistent in any case, without further cleanup. If someone comes > > up with a strong opinion here I would of course change it. > > Up to you. As long as the gnss node is named "gnss" I don't have a > strong opinion on the other names (as long as they follow the spec of > course). OK so I'm applying these two patches into omap-for-v5.1/dt. Thanks, Tony
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi index 02d8274a2f47..4ea0f7dc37c6 100644 --- a/arch/arm/boot/dts/omap3-gta04.dtsi +++ b/arch/arm/boot/dts/omap3-gta04.dtsi @@ -320,6 +320,12 @@ >; }; + gps_pins: pinmux_gps_pins { + pinctrl-single,pins = < + OMAP3_CORE1_IOPAD(0x2176, PIN_OUTPUT_PULLDOWN | MUX_MODE4) /* gpio145 */ + >; + }; + hdq_pins: hdq_pins { pinctrl-single,pins = < OMAP3_CORE1_IOPAD(0x21c6, PIN_INPUT_PULLUP | MUX_MODE0) /* i2c3_sda.hdq */ @@ -652,6 +658,14 @@ &uart2 { pinctrl-names = "default"; pinctrl-0 = <&uart2_pins>; + gnss: gnss { + compatible = "wi2wi,w2sg0004"; + pinctrl-names = "default"; + pinctrl-0 = <&gps_pins>; + sirf,onoff-gpios = <&gpio5 17 GPIO_ACTIVE_HIGH>; + lna-supply = <&vsim>; + vcc-supply = <&ldo_3v3>; + }; }; &uart3 {
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> --- Changes in v3: - converted to a patchset - added vcc-supply Changes in v2: - some s/gps/gnss/ - not added vcc-supply because the regulator is not modelled in dts at all w2sg0004 bindings are in next-20190129 arch/arm/boot/dts/omap3-gta04.dtsi | 14 ++++++++++++++ 1 file changed, 14 insertions(+)