From: Lokesh Vutla <lokeshvutla@ti.com>
To: Paul Barker <paul.barker@sancloud.com>, Tom Rini <trini@konsulko.com>
Cc: Peter Robinson <pbrobinson@gmail.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config
Date: Tue, 13 Jul 2021 11:28:29 +0530 [thread overview]
Message-ID: <72543b68-1599-cd8d-07ab-4a8a214671c8@ti.com> (raw)
In-Reply-To: <20210712172346.191c63f9.paul.barker@sancloud.com>
On 12/07/21 9:53 pm, Paul Barker wrote:
> On Thu, 17 Jun 2021 12:27:55 +0000
> Tom Rini <trini@konsulko.com> wrote:
>
>> On Thu, Jun 17, 2021 at 11:31:56AM +0100, Paul Barker wrote:
>>> On Thu, 17 Jun 2021 11:05:46 +0100
>>> Peter Robinson <pbrobinson@gmail.com> wrote:
>>>
>>>> On Thu, Jun 17, 2021 at 10:03 AM Paul Barker
>>>> <paul.barker@sancloud.com> wrote:
>>>>>
>>>>> Configuration which is shared between the BeagleBone Black and
>>>>> derivative boards like the Sancloud BeagleBone Enhanced (BBE) is
>>>>> moved to a common dtsi file to prevent duplication.
>>>>
>>>> Are these being sent upstream to the linux kernel?
>>>
>>> The upstream kernel already has am335x-boneblack-common.dtsi and
>>> am335x-sancloud-bbe.dts files, since 2016 and 2018 respectively. As
>>> these files fell out of sync over 4 years ago I've assumed there is no
>>> need to keep them in sync. We could try to resync things but that would
>>> lead to an unnecessary risk of breakage, I don't have every BeagleBone
>>> Black derivative board on hand to fully test such a resync.
>>
>> Adding in Lokesh. It would be really good to get as many of these files
>> back in sync again as possible and then keep them in sync periodically.
>> As I don't think there's been any breaking fixes in the dts files again,
>> there shouldn't be any problems.
>>
>
> Hi Tom,
>
> As there's been no reply from Lokesh I'd like to move forward with
> these updates if we can. I'm happy to resync the SanCloud dts files
> plus what we include, I think that will also involve copying over at
> least one more dt-bindings header as well.
>
> I'll send an updated series shortly.
Sorry for the delayed response as I was out of office last week.
yes, please sync the entire dts.
Thanks and regards,
Lokesh
>
> Thanks,
>
prev parent reply other threads:[~2021-07-13 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:02 [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Paul Barker
2021-06-17 9:02 ` [PATCH 2/4] arm: dts: am335x-sancloud-bbe: New dtb to support ethernet Paul Barker
2021-06-17 9:02 ` [PATCH 3/4] configs: am335x_evm: Support GbE PHYs Paul Barker
2021-06-17 9:02 ` [PATCH 4/4] configs: am335x_evm: Fix BeagleBone Green DTB selection Paul Barker
2021-06-17 10:05 ` [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Peter Robinson
2021-06-17 10:31 ` Paul Barker
2021-06-17 10:35 ` Peter Robinson
2021-06-17 10:49 ` Paul Barker
2021-06-17 12:27 ` Tom Rini
2021-07-12 16:23 ` Paul Barker
2021-07-13 5:58 ` Lokesh Vutla [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=72543b68-1599-cd8d-07ab-4a8a214671c8@ti.com \
--to=lokeshvutla@ti.com \
--cc=paul.barker@sancloud.com \
--cc=pbrobinson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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