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: Tue, 2 Feb 2021 16:34:03 +0100 [thread overview]
Message-ID: <41214211-a695-68c3-59a8-98d8a9fca55a@denx.de> (raw)
In-Reply-To: <CAHCN7xKzbOF7O4m-y4V=26fMQNE5PhBnHBDO5BXfqRY+-eijqw@mail.gmail.com>
On 2/2/21 2:01 PM, Adam Ford wrote:
> On Tue, Feb 2, 2021 at 4:11 AM Biju Das <biju.das.jz@bp.renesas.com> wrote:
>>
>> Hi Marek and Adam,
>>
>>> Subject: Re: [PATCH 1/5] arm: dts: r8a774a1: Import DTS queued for Linux
>>> 5.12-rc1
>>>
>>> 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.
>>>>
>>
>> Do we have usb2_clksel support in u-boot? If yes, it make sense to import from 5.12-rc1.
>> Similarly for other bits importing from kernel 5.12-rc1.
>>
>> May be rpc-spcif support available in u-boot. So we could import from 5.12-rc1.
>> For others like PCIe, ethernet the changes corresponding to dts is not present in driver.
>
> I think Marek has posted some rcar3 updates to support the PCIe.
RCar3 PCIe was supported for a while (years?), what I posted recently
were NVMe fixes.
> I
> am hopeful that it will work on the RZ/G2 series.
> I have rpc-spcif enabled and my plan was to post some updated configs
> with it enabled once the updated configs had been merged.
RPC is drivers/mtd/renesas_rpc_hf.c and drivers/spi/renesas_rpc_spi.c ?
[...]
prev parent reply other threads:[~2021-02-02 15:34 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
2021-02-02 10:11 ` Biju Das
2021-02-02 13:01 ` Adam Ford
2021-02-02 15:34 ` Marek Vasut [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=41214211-a695-68c3-59a8-98d8a9fca55a@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