[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200602135155.GE37466@atomide.com>
Date: Tue, 2 Jun 2020 06:51:55 -0700
From: Tony Lindgren <tony@...mide.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Drew Fustini <drew@...gleboard.org>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org,
BenoƮt Cousson <bcousson@...libre.com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
Santosh Shilimkar <ssantosh@...nel.org>,
Suman Anna <s-anna@...com>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: AM33xx-l4: add gpio-ranges
* Grygorii Strashko <grygorii.strashko@...com> [200602 13:44]:
>
>
> On 02/06/2020 16:14, Drew Fustini wrote:
> > Add gpio-ranges properties to the gpio controller nodes.
> >
> > These gpio-ranges were created based on "Table 9-10. CONTROL_MODULE
> > REGISTERS" in the "AM335x Technical Reference Manual" [0] and "Table
> > 4-2. Pin Attributes" in the "AM335x Sitara Processor datasheet" [1].
> > A csv file with this data is available for reference [2].
>
> It will be good if you can explain not only "what" is changed, but
> also "why" it's needed in commit message.
Also, please check (again) that this is the same for all the am3
variants. For omap3, we had different pad assignments even between
SoC revisions. Different pad routings should be easy to deal with
in the dts if needed though.
Regards,
Tony
Powered by blists - more mailing lists