linux-kernel - Re: [PATCH 1/2] ARM: dts: am335x: Replace numeric pinmux address with macro defines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <234521ee-3d8e-b413-65dd-5eefd44486d8@ti.com>
Date:   Thu, 3 May 2018 10:52:39 -0500
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Tony Lindgren <tony@...mide.com>,
        Christina Quast <cquast@...libre.com>
CC:     <linux-omap@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <narmstrong@...libre.com>,
        Oleg Kokorin <ole2mail@...l.com>
Subject: Re: [PATCH 1/2] ARM: dts: am335x: Replace numeric pinmux address with
 macro defines



On 04/30/2018 12:31 PM, Tony Lindgren wrote:
> Hi,
> 
> * Christina Quast <cquast@...libre.com> [180430 11:23]:
>> The values are extraced from the "AM335x SitaraTM Processors Technical
>> Reference Manual", Section 9.3.1 CONTROL_MODULE Registers, based on the
>> file autogenerated by TI PinMux.
> 
> This certainly makes things easier to mux :)
> 
> Have you verified that the registers are the same across all am335x
> models and different revisions?
> 
> It used to be that different SoC revisions could have different
> amount of registers and also different options in some cases.
> 
>> +#define AM335X_CONTROL_REVISION			0x0
>> +#define AM335X_CONTROL_HWINFO			0x4
>> +#define AM335X_CONTROL_SYSCONFIG		0x10
>> +#define AM335X_CONTROL_STATUS			0x40
> 
> You should only list the padconf mux registers here, no need to
> list any of the controller registers.
> 

To be honest, I do think it's right thing to do - DT by itself is
documentation and previously DT maintainers were not very happy regarding
introducing more defines instead of const.

Adding such defines will introduce big headers in Linux common or  
platform folders again which we've just got rid of. 

If smth is unclear - comments can be used in DT.

Just my 5c.


-- 
regards,
-grygorii