From: Andre Heider <a.heider@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] arm64: dts: armada-3720-espressobin: sync with downstream
Date: Fri, 4 Sep 2020 17:36:18 +0200 [thread overview]
Message-ID: <6dd67319-d843-7a86-2a05-30a6757bca3d@gmail.com> (raw)
In-Reply-To: <33127c92-3463-9d10-2484-c13a5825f36e@denx.de>
On 04/09/2020 14:40, Stefan Roese wrote:
> Hi Andre,
>
> On 04.09.20 14:35, Andre Heider wrote:
>
> <snip>
>
>>> First I though that you have been syncing the file with the Linux kernel
>>> version. But now I see that its sync'ed with downstream U-Boot most
>>> likely. As for the license of the file: The Linux kernel version has
>>> this SPDX tag:
>>>
>>> // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>>>
>>> Changing this to this tag would haven been fine (AFAICT). But using a
>>> diffent one from a downstream U-Boot repository is a bit troublesome
>>> for my taste.
>>>
>>> Can't you sync with Linux dts/dtsi files instead at some point?
>>
>> at some point, yes. As far as I understand that's not yet possible due
>> to the comphy driver. Quoting Marek's cover letter "[PATCH
>> u-boot-marvell 00/11] Armada 37xx: port comphy to generic-phys (PLEASE
>> TEST)" from 19th April:
>>
>> ?> I have ported the COMPHY and UTMI PHY drivers from Linux to U-Boot.
>> ?> With this we are able to abandon the current comphy_a3700 driver,
>> which
>> ?> is incompatible with Linux' device trees. So if we want to have DTS
>> ?> files for A3720 boards identical to Linux', we have to do this.
>>
>> So unfortunately we can't use Linux' dts files for a3700 yet. Marek
>> said he plans to work on that set again in the near future, so
>> hopefully that lands rather sooner than later ;)
>
> Ah, thanks. I remember now. ;)
>
> Can you then please drop the sync with the downstream dts and better
> only make the necessary changes for eMMC? In a git bisectable way
> please?
Sure, I've just sent v2, completely redone. That also prepares synching
from Linux, actually already imports two dts from from there.
Regards,
Andre
next prev parent reply other threads:[~2020-09-04 15:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 3:34 [PATCH 1/2] arm64: dts: armada-3720-espressobin: sync with downstream Andre Heider
2020-08-31 3:34 ` [PATCH 2/2] arm64: dts: armada-3720-espressobin-emmc: add emmc dts Andre Heider
2020-08-31 6:33 ` [PATCH v2 2/2] arm64: mvebu: a37xx: Add support for EspressoBIN with eMMC Andre Heider
2020-08-31 7:55 ` Pali Rohár
2020-08-31 8:21 ` Andre Heider
2020-08-31 8:27 ` Pali Rohár
2020-08-31 8:41 ` Andre Heider
2020-09-01 7:03 ` [PATCH v3 " Andre Heider
2020-09-01 20:02 ` Pali Rohár
2020-09-04 9:02 ` Stefan Roese
2020-08-31 7:53 ` [PATCH 1/2] arm64: dts: armada-3720-espressobin: sync with downstream Pali Rohár
2020-08-31 8:17 ` Andre Heider
2020-09-04 12:02 ` Stefan Roese
2020-09-04 12:35 ` Andre Heider
2020-09-04 12:40 ` Stefan Roese
2020-09-04 15:36 ` Andre Heider [this message]
2020-09-06 9:21 ` Pali Rohár
2020-09-06 16:03 ` Peter Robinson
2020-09-06 16:11 ` Pali Rohár
2020-08-31 8:01 ` Pali Rohár
2020-08-31 8:17 ` Andre Heider
2020-08-31 8:46 ` Pali Rohár
2020-08-31 9:59 ` Andre Heider
2020-09-01 20:00 ` Pali Rohár
2020-09-04 9:01 ` Stefan Roese
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=6dd67319-d843-7a86-2a05-30a6757bca3d@gmail.com \
--to=a.heider@gmail.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