From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/5] arm: dts: r8a774a1: Import DTS queued for Linux 5.12-rc1
Date: Mon, 1 Feb 2021 21:50:23 +0100 [thread overview]
Message-ID: <c15f345a-d6e9-08b4-d978-0fbae0056cd0@denx.de> (raw)
In-Reply-To: <CAHCN7xLwKXbSMPbnxU=+6xL117u=Sr37J5kjZ1yumkGZjMkC9g@mail.gmail.com>
On 2/1/21 4:19 PM, Adam Ford wrote:
> On Mon, Jan 25, 2021 at 6:40 AM Marek Vasut <marex@denx.de> wrote:
>>
>> On 1/25/21 12:22 AM, Adam Ford wrote:
>>> On Sun, Jan 24, 2021 at 11:10 AM Marek Vasut <marex@denx.de> wrote:
>>>>
>>>> On 1/13/21 12:52 AM, Adam Ford wrote:
>>>>> Update the RZ/G2M dtsi and r8a774a1-beacon-rzg2m-kit kit
>>>>> from Renesas repo destined to become 5.12-rc1.
>>>>
>>>> I picked a DT sync for Linux 5.10 from Biju (on CC), does your board
>>>> need something from 5.12-rc1 or can it be based on 5.10 too ?
>>>
>>> I honestly don't remember. I had to unexpectedly leave town for this
>>> week due to a funeral, and I won't be near a Linux development
>>> computer to run tests until Feb 1, so I don't know if the board will
>>> build using 5.10 or not. Sorry I don't have a better answer.
>>
>> Lets revisit this later then.
>
> I tested the Beacon boards, but they have a dependency on usb2_clksel
> that is not present in the 5.10 device tree.
> I also noticed that I forgot to include versaclock.h dt-binding file
> from the kernel, so the Beacon boards don't build for that too.
>
> I can submit a V2 with the binding file included, or I can submit the
> dt-binding file now and wait on the Beacon boards until that file has
> been merged, or I can redo the device tree in a custom way to work the
> 5.10 and not use the veraclock dt-bindings since there is no
> versaclock driver in U-Boot anyway. You may have an alternative as
> well.
Can you try to figure out the best option with Biju , who is in charge
of all the RZG stuff ? Either way works for me.
You also likely want to roll V2 out soon, since the RC1 is out. I would
still like to pick it for 2021.04 .
next prev parent reply other threads:[~2021-02-01 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 23:52 [PATCH 1/5] arm: dts: r8a774a1: Import DTS queued for Linux 5.12-rc1 Adam Ford
2021-01-12 23:52 ` [PATCH 2/5] arm: dts: r8a774e1: " Adam Ford
2021-01-12 23:52 ` [PATCH 3/5] arm: dts: r8a774b1: " Adam Ford
2021-01-12 23:52 ` [PATCH 4/5] ARM: rmobile: Add Beacon EmbeddedWorks RZG2N Dev Kit Adam Ford
2021-01-12 23:52 ` [PATCH 5/5] ARM: rmobile: Add Beacon EmbeddedWorks RZG2H " Adam Ford
2021-01-24 17:10 ` [PATCH 1/5] arm: dts: r8a774a1: Import DTS queued for Linux 5.12-rc1 Marek Vasut
2021-01-24 23:22 ` Adam Ford
2021-01-25 12:39 ` Marek Vasut
2021-02-01 15:19 ` Adam Ford
2021-02-01 20:50 ` Marek Vasut [this message]
2021-02-02 10:11 ` Biju Das
2021-02-02 13:01 ` Adam Ford
2021-02-02 15:34 ` 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=c15f345a-d6e9-08b4-d978-0fbae0056cd0@denx.de \
--to=marex@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).