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@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@xxxxxxx 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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
