From: Marek Vasut <marex@denx.de>
To: Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Patrick DELAUNAY <patrick.delaunay@st.com>,
Patrice CHOTARD <patrice.chotard@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] [RFC] ARM: dts: stm32: Add DTs for STM32MP15x variants of the DH SOM and PDK2
Date: Tue, 24 Mar 2020 15:58:44 +0100 [thread overview]
Message-ID: <7723c340-067b-d780-0eb1-c47d50b11ee9@denx.de> (raw)
In-Reply-To: <9492207e929c4185bda5a709ad879c15@SFHDAG3NODE2.st.com>
On 3/24/20 3:39 PM, Alexandre TORGUE wrote:
>
>
>> -----Original Message-----
>> From: Marek Vasut <marex@denx.de>
>> Sent: mardi 24 mars 2020 15:31
>> To: Alexandre TORGUE <alexandre.torgue@st.com>; linux-arm-
>> kernel@lists.infradead.org
>> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>; Patrice CHOTARD
>> <patrice.chotard@st.com>; Patrick DELAUNAY <patrick.delaunay@st.com>; linux-
>> stm32@st-md-mailman.stormreply.com
>> Subject: Re: [PATCH] [RFC] ARM: dts: stm32: Add DTs for STM32MP15x variants
>> of the DH SOM and PDK2
>>
>> On 3/24/20 3:28 PM, Alexandre Torgue wrote:
>>>
>>>
>>> On 3/24/20 3:15 PM, Marek Vasut wrote:
>>>> On 3/24/20 3:07 PM, Alexandre Torgue wrote:
>>>>>
>>>>>
>>>>> On 3/24/20 2:22 PM, Marek Vasut wrote:
>>>>>> On 3/24/20 2:04 PM, Alexandre Torgue wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 3/23/20 3:31 AM, Marek Vasut wrote:
>>>>>>>> The DH PDK2 can be populated with SoM with any STM32MP15x variant.
>>>>>>>> Add the DTs describing the remaining combinations.
>>>>>>>>
>>>>>>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>>>>>>> Cc: Alexandre Torgue <alexandre.torgue@st.com>
>>>>>>>> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
>>>>>>>> Cc: Patrice Chotard <patrice.chotard@st.com>
>>>>>>>> Cc: Patrick Delaunay <patrick.delaunay@st.com>
>>>>>>>> Cc: linux-stm32@st-md-mailman.stormreply.com
>>>>>>>> To: linux-arm-kernel@lists.infradead.org
>>>>>>>> ---
>>>>>>>> NOTE: Is there a better way to do this than to have this kind of
>>>>>>>> a
>>>>>>>> combinatorial explosion of DTs ?
>>>>>>>
>>>>>>> I have no better idea. Question was the same for stm32 boards, and
>>>>>>> I chose to take this option.
>>>>>>
>>>>>> One option would be to just have DT for the most feature-complete
>>>>>> option
>>>>>> (157) and then have U-Boot remove the nodes for HW which is not
>>>>>> present on the particular SoC option if it's one of the more
>>>>>> limited ones (153, 151).
>>>>>>
>>>>>
>>>>> Yes it was a possibility that I discussed with kevin H. at the
>>>>> latest ELCE but at the end the best way to follow was to enhance
>>>>> number of dts files. The best would be to have dedicated folders but
>>>>> it is another story.
>>>>
>>>> Or use DT overlays somehow ? U-Boot can apply DTOs onto DT before
>>>> booting Linux.
>>>>
>>>> Having tons of DTs on a system is a lot of duplication, I don't
>>>> really like that.
>>>
>>> I agree that to maintain it's a nightmare, but it's a way to help DT users.
>>>
>>>>
>>>> But for starters, feel free to review this patch.
>>>>
>>>
>>> Your patch sounds good.
>>
>> Then feel free to apply it, thanks.
>>
>> btw don't you have a "next" tree somewhere with all the patches queued up for
>> next release ? If I rebase on linux next, I still have quite a few stm32mp1 DT
>> patches in my tree which are presumably applied, but I don't see them in linux next.
>
>
> Yes but it is not merged into Linux-next. See: git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git
>
> Branch stm32-next
Thanks. Wouldn't it be more convenient and receive more testing if it
were to be merged into next, just like the other trees are ?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-24 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 2:31 [PATCH] [RFC] ARM: dts: stm32: Add DTs for STM32MP15x variants of the DH SOM and PDK2 Marek Vasut
2020-03-24 13:04 ` Alexandre Torgue
2020-03-24 13:22 ` Marek Vasut
2020-03-24 14:07 ` Alexandre Torgue
2020-03-24 14:15 ` Marek Vasut
2020-03-24 14:28 ` Alexandre Torgue
2020-03-24 14:31 ` Marek Vasut
2020-03-24 14:39 ` Alexandre TORGUE
2020-03-24 14:58 ` Marek Vasut [this message]
2020-03-24 15:17 ` Alexandre Torgue
2020-03-24 15:22 ` 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=7723c340-067b-d780-0eb1-c47d50b11ee9@denx.de \
--to=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).