From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 9/9] ARM: dts: stm32: add initial support of stm32mp157c eval board
Date: Thu, 21 Dec 2017 11:44:55 +0100 [thread overview]
Message-ID: <33a7afc4-9282-5359-1f80-ef9f3da93c38@st.com> (raw)
In-Reply-To: <CACRpkdYE+u1o_KDDihX7=7RLNDkkFDOCFsQtBKBZW0i6123ZoQ@mail.gmail.com>
On 12/21/2017 10:18 AM, Linus Walleij wrote:
> On Wed, Dec 20, 2017 at 10:19 AM, Alexandre Torgue
> <alexandre.torgue@st.com> wrote:
>> On 12/20/2017 08:44 AM, Linus Walleij wrote:
>
>>> gpio-line-names = "foo", "bar" ...;
>>>
>>> See for example
>>> arch/arm/boot/dts/bcm2835-rpi-a.dts
>>> arch/arm/boot/dts/ste-snowball.dts
> (...)
>>
>> It looks like useful for pins used as gpio line. Are you saying that we also
>> have to describe pins used as Alternate Function ?
>
> No. The use of the names is up to the platform maintainer (you),
> leaving a blank string for non-GPIO lines is just fine.
>
> Some platforms add the name of the actual function used by the
> line on the design, if it is not GPIO, sometimes something in
> brachets like "[i2c0-SDA]" that says what it is used for and explains
> why you can't use it for GPIO on this setup.
>
> But just leaving it blank is just as good.
Ok thanks Linus. I will take it into account. It could be useful to add
it for MCU and future MPU boards.
Regards
Alex
>
> Yours,
> Linus Walleij
>
prev parent reply other threads:[~2017-12-21 10:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:17 [PATCH V2 0/9] ARM: stm32: add initial STM32MPU support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 1/9] devicetree: bindings: Document supported STM32 SoC family Ludovic Barre
2017-12-20 7:33 ` Linus Walleij
2017-12-18 15:17 ` [PATCH V2 2/9] Documentation: arm: stm32: move to rst format Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 3/9] ARM: stm32: prepare stm32 family to welcome armv7 architecture Ludovic Barre
2017-12-18 20:24 ` Arnd Bergmann
2017-12-19 14:38 ` Alexandre Torgue
2017-12-21 16:39 ` Ludovic BARRE
2017-12-21 20:48 ` Arnd Bergmann
2017-12-19 14:43 ` Ludovic BARRE
2017-12-19 15:26 ` Arnd Bergmann
2017-12-19 15:54 ` Ludovic BARRE
2017-12-18 15:17 ` [PATCH V2 4/9] devicetree: bindings: stm32: add support of STM32MP157 Ludovic Barre
2017-12-20 18:24 ` Rob Herring
2017-12-18 15:17 ` [PATCH V2 5/9] ARM: stm32: add initial support for STM32MP157 Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 6/9] pinctrl: stm32: Add STM32MP157 MPU support Ludovic Barre
2017-12-20 7:38 ` Linus Walleij
2017-12-18 15:17 ` [PATCH V2 7/9] ARM: configs: multi_v7: add stm32 support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 8/9] ARM: dts: stm32: add stm32mp157c initial support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 9/9] ARM: dts: stm32: add initial support of stm32mp157c eval board Ludovic Barre
2017-12-18 20:20 ` Arnd Bergmann
2017-12-19 8:45 ` Ludovic BARRE
2017-12-19 9:17 ` Alexandre Torgue
2017-12-20 7:44 ` Linus Walleij
2017-12-20 9:19 ` Alexandre Torgue
2017-12-21 9:18 ` Linus Walleij
2017-12-21 10:44 ` Alexandre Torgue [this message]
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=33a7afc4-9282-5359-1f80-ef9f3da93c38@st.com \
--to=alexandre.torgue@st.com \
--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