linux-kernel - Re: [RFC PATCH] ARM: dts: stm32: change pinctrl bindings definition

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: <25cebb45-b770-c0b4-a478-13b01b5cfd0e@st.com>
Date:   Mon, 17 Jul 2017 13:19:11 +0200
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Arnd Bergmann <arnd@...db.de>
CC:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Russell King <linux@...linux.org.uk>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] ARM: dts: stm32: change pinctrl bindings definition

Hi

On 07/17/2017 01:15 PM, Arnd Bergmann wrote:
> On Mon, Jul 17, 2017 at 1:00 PM, Alexandre TORGUE
> <alexandre.torgue@...com> wrote:
>> blabla
>>
>> Signed-off-by: Alexandre TORGUE <alexandre.torgue@...com>
> 
> You may want to provide a little more detail here ;-)
> 
Oh!! Sorry, I changed it but no sent the good commit :).

Please translate blablable by:

Initially each pin was declared in 
"include/dt-bindings/stm32f429-pinfunc.h"and each definition contained 
SOC names (ex: STM32F429_PA9_FUNC_USART1_TX).
Since this approach was approved, the number of supported MCU has
increased (STM32F429/STM32F469/STM32f746/STM32H743). To avoid to add a 
new file in "include/dt-bindings" each time a new STM32 SOC arrives I 
propose a new approach which consist to use a macro to define pin muxing 
in device tree. All STM32 will use the common macro to define pinmux. 
Furthermore, it will make easy maintenance and integration of new SOC.

Regards
Alex

>           Arnd
>