All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, alistair@alistair23.me
Subject: Re: [PATCH v3] ARM: dts: imx: e60k02: Add touchscreen
Date: Fri, 11 Nov 2022 10:54:38 +0100	[thread overview]
Message-ID: <20221111105438.26c477ae@aktux> (raw)
In-Reply-To: <20221111091223.if2ahwz67vkf72ba@pengutronix.de>

Hi Marco,

On Fri, 11 Nov 2022 10:12:23 +0100
Marco Felsch <m.felsch@pengutronix.de> wrote:

> Hi Andreas,
> 
> On 22-11-09, Andreas Kemnade wrote:
> > On Wed, 9 Nov 2022 10:23:50 +0100
> > Marco Felsch <m.felsch@pengutronix.de> wrote:
> >   
> > > Hi Andreas,
> > > 
> > > On 22-11-08, Andreas Kemnade wrote:  
> > > > Add the touchscreen now, since the driver is available.
> > > > 
> > > > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > > > ---
> > > > Changes in v3: no phandles pointing from dtsi to dts    
> > > 
> > > Thanks for this change...
> > >   
> > > > Changes in v2: fix pinmux naming
> > > > 
> > > >  arch/arm/boot/dts/e60k02.dtsi              |  9 ++++++++-
> > > >  arch/arm/boot/dts/imx6sl-tolino-shine3.dts | 12 ++++++++++++
> > > >  arch/arm/boot/dts/imx6sll-kobo-clarahd.dts | 12 ++++++++++++
> > > >  3 files changed, 32 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/arch/arm/boot/dts/e60k02.dtsi
> > > > b/arch/arm/boot/dts/e60k02.dtsi index 935e2359f8df..99091db3ab2a
> > > > 100644 --- a/arch/arm/boot/dts/e60k02.dtsi
> > > > +++ b/arch/arm/boot/dts/e60k02.dtsi
> > > > @@ -104,7 +104,14 @@ &i2c2 {
> > > >  	clock-frequency = <100000>;
> > > >  	status = "okay";
> > > >  
> > > > -	/* TODO: CYTTSP5 touch controller at 0x24 */
> > > > +	cyttsp5: touchscreen@24 {
> > > > +		compatible = "cypress,tt21000";
> > > > +		reg = <0x24>;
> > > > +		interrupt-parent = <&gpio5>;
> > > > +		interrupts = <6 IRQ_TYPE_EDGE_FALLING>;
> > > > +		reset-gpios = <&gpio5 13 GPIO_ACTIVE_LOW>;
> > > > +		vdd-supply = <&ldo5_reg>;
> > > > +	};    
> > > 
> > > but we still have a cross-reference to the .dtsi file here. Therefore
> > > I said to move the interrupt/reset-gpio into the dts file too. I know
> > > this is a kind of a nitpick but I really don't like such
> > > cross-references.
> > >   
> > hmm. &gpio5 references to imx6sl[l].dtsi, not dts, so what is the
> > problem here?  
> 
> Sorry for the missunderstanding, I didn't mean the phandle. I mean the
> mux setting which is done in the dts right? I'm just not a fan of
> muxing pins in one file an using those 'assumptions' in others. Except
> for platforms like the imx8mm-evk which is exactly the same hardware and
> only differs in the RAM they used. But you have two different platforms
> right?
> 
Same board, same PCB marking, the only spotted difference is the name on the
case and the SoC (which is pin-compatible, so GPIOs will be all the same).

In the case of different hardware platforms I would understand your
ruffled feathers.

Regards,
Andreas

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Kemnade <andreas@kemnade.info>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, alistair@alistair23.me
Subject: Re: [PATCH v3] ARM: dts: imx: e60k02: Add touchscreen
Date: Fri, 11 Nov 2022 10:54:38 +0100	[thread overview]
Message-ID: <20221111105438.26c477ae@aktux> (raw)
In-Reply-To: <20221111091223.if2ahwz67vkf72ba@pengutronix.de>

Hi Marco,

On Fri, 11 Nov 2022 10:12:23 +0100
Marco Felsch <m.felsch@pengutronix.de> wrote:

> Hi Andreas,
> 
> On 22-11-09, Andreas Kemnade wrote:
> > On Wed, 9 Nov 2022 10:23:50 +0100
> > Marco Felsch <m.felsch@pengutronix.de> wrote:
> >   
> > > Hi Andreas,
> > > 
> > > On 22-11-08, Andreas Kemnade wrote:  
> > > > Add the touchscreen now, since the driver is available.
> > > > 
> > > > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > > > ---
> > > > Changes in v3: no phandles pointing from dtsi to dts    
> > > 
> > > Thanks for this change...
> > >   
> > > > Changes in v2: fix pinmux naming
> > > > 
> > > >  arch/arm/boot/dts/e60k02.dtsi              |  9 ++++++++-
> > > >  arch/arm/boot/dts/imx6sl-tolino-shine3.dts | 12 ++++++++++++
> > > >  arch/arm/boot/dts/imx6sll-kobo-clarahd.dts | 12 ++++++++++++
> > > >  3 files changed, 32 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/arch/arm/boot/dts/e60k02.dtsi
> > > > b/arch/arm/boot/dts/e60k02.dtsi index 935e2359f8df..99091db3ab2a
> > > > 100644 --- a/arch/arm/boot/dts/e60k02.dtsi
> > > > +++ b/arch/arm/boot/dts/e60k02.dtsi
> > > > @@ -104,7 +104,14 @@ &i2c2 {
> > > >  	clock-frequency = <100000>;
> > > >  	status = "okay";
> > > >  
> > > > -	/* TODO: CYTTSP5 touch controller at 0x24 */
> > > > +	cyttsp5: touchscreen@24 {
> > > > +		compatible = "cypress,tt21000";
> > > > +		reg = <0x24>;
> > > > +		interrupt-parent = <&gpio5>;
> > > > +		interrupts = <6 IRQ_TYPE_EDGE_FALLING>;
> > > > +		reset-gpios = <&gpio5 13 GPIO_ACTIVE_LOW>;
> > > > +		vdd-supply = <&ldo5_reg>;
> > > > +	};    
> > > 
> > > but we still have a cross-reference to the .dtsi file here. Therefore
> > > I said to move the interrupt/reset-gpio into the dts file too. I know
> > > this is a kind of a nitpick but I really don't like such
> > > cross-references.
> > >   
> > hmm. &gpio5 references to imx6sl[l].dtsi, not dts, so what is the
> > problem here?  
> 
> Sorry for the missunderstanding, I didn't mean the phandle. I mean the
> mux setting which is done in the dts right? I'm just not a fan of
> muxing pins in one file an using those 'assumptions' in others. Except
> for platforms like the imx8mm-evk which is exactly the same hardware and
> only differs in the RAM they used. But you have two different platforms
> right?
> 
Same board, same PCB marking, the only spotted difference is the name on the
case and the SoC (which is pin-compatible, so GPIOs will be all the same).

In the case of different hardware platforms I would understand your
ruffled feathers.

Regards,
Andreas

  reply	other threads:[~2022-11-11  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:15 [PATCH v3] ARM: dts: imx: e60k02: Add touchscreen Andreas Kemnade
2022-11-08 19:15 ` Andreas Kemnade
2022-11-09  9:23 ` Marco Felsch
2022-11-09  9:23   ` Marco Felsch
2022-11-09 11:45   ` Andreas Kemnade
2022-11-09 11:45     ` Andreas Kemnade
2022-11-11  9:12     ` Marco Felsch
2022-11-11  9:12       ` Marco Felsch
2022-11-11  9:54       ` Andreas Kemnade [this message]
2022-11-11  9:54         ` Andreas Kemnade
2022-11-11 15:38         ` Marco Felsch
2022-11-11 15:38           ` Marco Felsch

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=20221111105438.26c477ae@aktux \
    --to=andreas@kemnade.info \
    --cc=alistair@alistair23.me \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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.