All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Alexandre Torgue <alexandre.torgue@st.com>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Patrice CHOTARD <patrice.chotard@st.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: Patrick DELAUNAY <patrick.delaunay@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	"linux-stm32@st-md-mailman.stormreply.com"
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [Linux-stm32] [PATCH 07/22] ARM: dts: stm32: Add alternate pinmux for SDMMC2 pins 4-7
Date: Tue, 31 Mar 2020 18:44:58 +0200	[thread overview]
Message-ID: <9fb131ad-552e-61ad-75c2-5ebec501f356@denx.de> (raw)
In-Reply-To: <69bce6d4-129e-b9ea-8fa6-f33d9047e3c3@st.com>

On 3/31/20 6:39 PM, Alexandre Torgue wrote:

Hi,

[...]

>>> I agree, and I prefer to keep pins groups definition in
>>> stm32mp15-pinctrl.dtsi file. IMO, it is easier for users to find them in
>>> only one file. Actually, I already had this discussions with some guys
>>> "where pins groups have to be defined ?". For me (and maybe only for
>>> me), muxing is SOC dependent, I mean SoC provides a bunch a possible
>>> pinmux for each IPs. If we got enough memory spaces (and time to waste
>>> also) we could define all possible pinmux (AFx....) for each devices and
>>> let board users chose the good one (using stm32mp15-pictrl.dtsi as a
>>> database). In board file, you select one possible pin configuration
>>> (provided by the SoC) for your device according to your schematic.
>>> However you could append pin groups in board file to update bias,
>>> slewrate ...
>>> If your concern it to embed a bunch of not used pin configuration for a
>>> board, we could use /omit-if-no-ref/ tag on pin groups.
>>
>> Can we instead define pinmux the way e.g. iMX6 does , as separate pins ,
>> instead of pinmux groups ?
>>
> 
> Sorry but what would the advantage to do so ?

You'd have per-board pinmux which would be perfect fit for that board,
without potentially affecting other boards with changes, without hacking
various things like drive-strengths in board files, and without having
the combinatorial explosion of the current single pinmux file.

-- 
Best regards,
Marek Vasut

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-03-31 16:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 17:11 [PATCH 00/22] ARM: dts: stm32: Repair AV96 board Marek Vasut
2020-03-28 17:11 ` [PATCH 01/22] ARM: dts: stm32: Add alternate pinmux for ethernet RGMII Marek Vasut
2020-03-28 17:11 ` [PATCH 02/22] ARM: dts: stm32: Repair ethernet operation on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 03/22] ARM: dts: stm32: Add missing ethernet PHY reset " Marek Vasut
2020-03-28 17:11 ` [PATCH 04/22] ARM: dts: stm32: Add missing ethernet PHY skews " Marek Vasut
2020-03-28 17:11 ` [PATCH 05/22] ARM: dts: stm32: Add alternate pinmux for SDMMC1 direction pins Marek Vasut
2020-03-28 17:11 ` [PATCH 06/22] ARM: dts: stm32: Repair SDMMC1 operation on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 07/22] ARM: dts: stm32: Add alternate pinmux for SDMMC2 pins 4-7 Marek Vasut
2020-03-30 11:11   ` Patrice CHOTARD
2020-03-30 11:17     ` [Linux-stm32] " Ahmad Fatoum
2020-03-30 11:22       ` Marek Vasut
2020-03-30 11:37         ` Ahmad Fatoum
2020-03-30 11:45           ` Marek Vasut
2020-03-31  8:58             ` Alexandre Torgue
2020-03-31 13:38               ` Marek Vasut
2020-03-31 16:39                 ` Alexandre Torgue
2020-03-31 16:44                   ` Marek Vasut [this message]
2020-04-01  9:49                     ` Alexandre Torgue
2020-03-28 17:11 ` [PATCH 08/22] ARM: dts: stm32: Add eMMC attached to SDMMC2 on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 09/22] ARM: dts: stm32: Repair PMIC configuration " Marek Vasut
2020-03-28 17:11 ` [PATCH 10/22] ARM: dts: stm32: Repair PMIC interrupt " Marek Vasut
2020-03-28 17:11 ` [PATCH 11/22] ARM: dts: stm32: Add QSPI NOR " Marek Vasut
2020-03-28 17:11 ` [PATCH 12/22] ARM: dts: stm32: Add configuration EEPROM " Marek Vasut
2020-03-28 17:11 ` [PATCH 13/22] ARM: dts: stm32: Enable GPU " Marek Vasut
2020-03-28 17:11 ` [PATCH 14/22] ARM: dts: stm32: Add alternate pinmux for SDMMC3 pins Marek Vasut
2020-03-28 17:11 ` [PATCH 15/22] ARM: dts: stm32: Enable WiFi on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 16/22] ARM: dts: stm32: Add alternate pinmux for USART2 pins Marek Vasut
2020-03-28 17:11 ` [PATCH 17/22] ARM: dts: stm32: Enable Bluetooth on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 18/22] ARM: dts: stm32: Add alternate pinmux for LTDC pins Marek Vasut
2020-03-28 17:11 ` [PATCH 19/22] ARM: dts: stm32: Add bindings for HDMI video on AV96 Marek Vasut
2020-03-28 17:11 ` [PATCH 20/22] ARM: dts: stm32: Add bindings for audio " Marek Vasut
2020-03-28 17:11 ` [PATCH 21/22] ARM: dts: stm32: Add bindings for USB " Marek Vasut
2020-03-28 17:11 ` [PATCH 22/22] ARM: dts: stm32: Rename LEDs to match silkscreen " Marek Vasut

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=9fb131ad-552e-61ad-75c2-5ebec501f356@denx.de \
    --to=marex@denx.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=alexandre.torgue@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=patrice.chotard@st.com \
    --cc=patrick.delaunay@st.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.