devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Markus Niebel <Markus.Niebel@tq-group.com>,
	Rob Herring <robh+dt@kernel.org>,
	kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: imx6qdl: add TQMa6{S,Q,QP} SoM
Date: Mon, 28 Oct 2019 15:28:45 +0100	[thread overview]
Message-ID: <c98fcd3bbd4e2166b2938fd2f8fa6f1a5a270384.camel@pengutronix.de> (raw)
In-Reply-To: <20191026093356.GE14401@dragon>

Hi Shawn,

On Sat, 2019-10-26 at 17:34 +0800, Shawn Guo wrote:
> On Fri, Oct 11, 2019 at 04:36:49PM +0200, Philipp Zabel wrote:
> > From: Markus Niebel <Markus.Niebel@tq-group.com>
> > 
> > Add device trees for TQMa6S, TQMa6Q, and TQMa6QP embedded modules.
> > The A and B SoM variants are for hardware revisions that differ in
> > how the I2C devices are connected. For details, see [1].
> 
> It looks like a perfect case to be handled by DT overlay.
> Did you consider of using that?

I don't think using DT overlays is feasible. The EEPROM that could tell
us which variant we are running on is on the I2C bus that is different
between the two variants.

[...]
> > +&ecspi1 {
> > +	pinctrl-names = "default";
> > +	pinctrl-0 = <&pinctrl_ecspi1>;
> > +	fsl,spi-num-chipselects = <1>;
> 
> Obsolete property.
> 
> > +	cs-gpios = <&gpio3 19 0>;
> 
> GPIO_ACTIVE_HIGH
> 
> > +	status = "okay";
> > +
> > +	flash: m25p80@0 {
> 
> Node name should be generic, while label can be specific.
> 
> > +		status = "okay";
> 
> Not really needed.
> 
[...]
> > +&iomuxc {
> > +	tqma6 {
> 
> Drop this container node.
> 
[...]
> > +		pinctrl_i2c1_tqma6: i2c1-tqma6grp {
> 
> The '_tqma6' suffix isn't really useful.
> 
[...]
> > +&pmic {
> > +		pinctrl-names = "default";
> > +		pinctrl-0 = <&pinctrl_pmic>;
> > +		interrupt-parent = <&gpio6>;
> > +		interrupts = <10 8>;
> 
> IRQ_TYPE_LEVEL_LOW
> 
[...]
> > +	pmic: pf0100@8 {
> 
> Node name should be generic, while label can be specific.
> 
> > +		compatible = "fsl,pfuze100";
> > +		reg = <0x08>;
> > +	};
> > +
> > +	sensor0: lm75@48 {
> 
> Ditto
> 
> > +		compatible = "lm75";
> > +		reg = <0x48>;
> > +	};
> > +
> > +	eeprom0: m24c64@50 {
> 
> Ditto

Thank you, I'll fix these.

regards
Philipp


      reply	other threads:[~2019-10-28 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 14:36 [PATCH 1/3] ARM: dts: imx6qdl: add TQMa6{S,Q,QP} SoM Philipp Zabel
2019-10-11 14:36 ` [PATCH 2/3] ARM: dts: imx6qdl: add MBa6 mainboard with TQMa6{S, Q, QP} SoMs Philipp Zabel
2019-10-11 14:36 ` [PATCH 3/3] dt-bindings: arm: fsl: Add TQ TQMa6{S,Q,QP} on MBa6x Philipp Zabel
2019-10-26  9:34 ` [PATCH 1/3] ARM: dts: imx6qdl: add TQMa6{S,Q,QP} SoM Shawn Guo
2019-10-28 14:28   ` Philipp Zabel [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=c98fcd3bbd4e2166b2938fd2f8fa6f1a5a270384.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=Markus.Niebel@tq-group.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --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 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).