From: aisheng.dong@codeaurora.org (aisheng.dong at codeaurora.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm64: add basic DTS for i.MX8MQ
Date: Thu, 25 Jan 2018 17:48:41 +0800 [thread overview]
Message-ID: <ebc8b28d5c2948131cc187ac8177395c@codeaurora.org> (raw)
In-Reply-To: <1516713799.25726.21.camel@pengutronix.de>
Hi Lucas,
First of all, good to see this patch series in community.
Pengutronix has always been an active friendly contributor on IMX
upstream activities. You Did help us a lot!
On 2018-01-23 21:23, Lucas Stach wrote:
<snip>
>> > > > + #address-cells = <1>;
>> > > > + #size-cells = <1>;
>> > > > + ranges = <0x30000000 0x30000000 0x400000>;
>> > +
>> > > > > > + gpio1: gpio at 30200000 {
>> > + compatible = "nxp,imx8mq-gpio", "fsl,imx35-gpio";
>>
>> It looks a bit odd to have different vendor prefix for the same
>> device.
>> But we can understand the reason.??Just curious if this is what vendor
>> kernel does?
>
> No, I did it mostly to be consistent with the location of the DT files
> under "nxp". I'll change this to match the "freescale" location.
>
Vendor tree mostly is still using fsl,imx8mq-xx.
And many binding doc format is:"compatible : Should be "fsl,<soc>-gpio".
So we can't use 'nxp' prefix here without changing binding doc.
Then if we decided to use 'fsl' prefix, probably we may want to fix the
rest of them in this file as well.
And i see the dtsi file does not include Freescale/NXP copyright,
is there a reason?
BTW it's quite strange that my gmail did not receive your MX8MQ patch
series except clk part.
Lucas, Could you help have me CCed next time?
I'd like to help review and test the patch series.
For this time, can you help send them all to me as attachment?
(You can also send all IMX related patches to linux-imx at nxp.com maillist
i created recently for tracking all IMX related upstream activities.
Most Freescale/NXP driver owners are in this list that could help on
the review. Shawn, do you think if i can put it in MAINTAINER file?)
Regards
Dong Aisheng
> Regards,
> Lucas
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-01-25 9:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 18:32 [PATCH 1/4] ARM64: add basic Kconfig symbols for i.MX8 Lucas Stach
2018-01-17 18:32 ` [PATCH 2/4] arm64: add basic DTS for i.MX8MQ Lucas Stach
2018-01-22 11:51 ` Arnd Bergmann
2018-01-22 11:57 ` Fabio Estevam
2018-01-22 14:47 ` Shawn Guo
2018-01-22 15:11 ` Arnd Bergmann
2018-01-22 17:50 ` Lucas Stach
2018-01-23 1:40 ` Shawn Guo
2018-01-23 10:36 ` Shawn Guo
2018-01-23 13:23 ` Lucas Stach
2018-01-25 9:48 ` aisheng.dong at codeaurora.org [this message]
2018-01-25 10:27 ` Lucas Stach
2018-01-25 12:34 ` Dong Aisheng
2018-02-02 7:27 ` Shawn Guo
2018-01-29 17:45 ` Rob Herring
2018-01-29 17:55 ` Rob Herring
2018-01-29 18:00 ` Lucas Stach
2018-01-30 14:55 ` Rob Herring
2018-01-17 18:32 ` [PATCH 3/4] arm64: add support for i.MX8M EVK board Lucas Stach
2018-01-22 11:58 ` Fabio Estevam
2018-01-23 10:39 ` Shawn Guo
2018-01-25 10:10 ` aisheng.dong at codeaurora.org
2018-01-25 10:31 ` Lucas Stach
2018-01-25 10:49 ` Dong Aisheng
2018-01-25 11:09 ` Lucas Stach
2018-01-25 13:03 ` Dong Aisheng
2018-01-25 18:03 ` Lucas Stach
2018-01-26 3:06 ` A.s. Dong
2018-01-24 14:47 ` Baruch Siach
2018-01-25 9:52 ` Baruch Siach
2018-01-29 17:52 ` Rob Herring
2018-01-17 18:32 ` [PATCH 4/4] MAINTAINERS: add i.MX8 DT path to i.MX architecture Lucas Stach
2018-01-22 11:58 ` Fabio Estevam
2018-01-22 11:53 ` [PATCH 1/4] ARM64: add basic Kconfig symbols for i.MX8 Fabio Estevam
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=ebc8b28d5c2948131cc187ac8177395c@codeaurora.org \
--to=aisheng.dong@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).