From: Kever Yang <kever.yang@rock-chips.com>
To: Quentin Schulz <quentin.schulz@cherry.de>,
Quentin Schulz <foss+uboot@0leil.net>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
Heiko Stuebner <heiko.stuebner@cherry.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v2] rockchip: add support for Theobroma Systems SOM-RK3588-Q7 Tiger module
Date: Wed, 8 May 2024 18:00:43 +0800 [thread overview]
Message-ID: <60ddc200-c3bb-41db-8d94-51761893cfde@rock-chips.com> (raw)
In-Reply-To: <59c3ee19-f1c5-425d-912d-d418c7a2990b@cherry.de>
Hi Quentin,
On 2024/5/8 16:34, Quentin Schulz wrote:
> Hi Kever,
>
> On 5/8/24 4:42 AM, Kever Yang wrote:
>> Hi Quentin,
>>
>> Could you please update this patch with OF_UPSTREAM support?
>>
>
> No, I cannot yet :/
>
> Tiger is only available in Linux kernel v6.9-rcX and dts/ in U-Boot is
> currently at v6.8.
I see, then we may need to support the board without OF_UPSTREAM during
the dts is available
in kernel tree but not available in U-Boot dts/upstream.
>
> What are we supposed to do for this then?
>
> Would bumping dts/ to an -rc tag be ok for U-Boot?
Hi Tom,
What's policy of the dts/upstream suppose to update? This is the
typical issue there is gap
between the dts merge in mainline kernel and available in next release.
Thanks,
- Kever
> After all, those are rc and not "stable" branches. Do we need to wait
> for the actual kernel release before bumping dts/ (so wait for up to 2
> months before supporting a board in U-Boot)? Should we have an
> intermediate solution where we use the "old" model (NOT OF_UPSTREAM)
> until we bump dts/ to the latest kernel release and the DTS is
> available through OF_UPSTREAM?
>
> Cheers,
> Quentin
next prev parent reply other threads:[~2024-05-08 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:18 [PATCH v2] rockchip: add support for Theobroma Systems SOM-RK3588-Q7 Tiger module Quentin Schulz
2024-05-08 2:42 ` Kever Yang
2024-05-08 8:34 ` Quentin Schulz
2024-05-08 10:00 ` Kever Yang [this message]
2024-05-16 15:38 ` Heiko Stübner
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=60ddc200-c3bb-41db-8d94-51761893cfde@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=foss+uboot@0leil.net \
--cc=heiko.stuebner@cherry.de \
--cc=klaus.goger@theobroma-systems.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--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