From: Shane Francis <bigbeeshane@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
heiko@sntech.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: clock: update rk3588 clock definitions
Date: Sun, 26 Mar 2023 18:51:29 +0100 [thread overview]
Message-ID: <CABnpCuA7V9ti6BOoz+3Mq-f=PwgxL2K7rOhjo6tJ4QquSZbaSA@mail.gmail.com> (raw)
In-Reply-To: <717bfba9-1d70-ef09-9193-853a57117926@linaro.org>
> Bootloader also does not use mainline DTS, so where is exactly the problem?
In this case uboot does load the target DTB, and it seems a common
function in rockchips
downstream boot process, see :
https://github.com/rockchip-linux/u-boot/blob/ef1dd650042f61915c4859ecc94623a09a3529fa/arch/arm/mach-rockchip/kernel_dtb.c#L70
It's a pretty nasty process, but unfortunately some devices will be
stuck with it I guess, and in
those cases they will have issues booting a mainline kernel.
Regards
On Sun, Mar 26, 2023 at 6:23 PM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> On 26/03/2023 18:59, Shane Francis wrote:
> > Hi Krzysztof
> >
> >
> >> So mention this in the commit msg.
> >
> >> Then commit msg should also mention it.
> >
> > Sorry for not expanding on this more in the initial commit message, I will
> > expand on this in the next patch set.
> >
> > However I think in general for most modern platforms it can be assumed
> > that replacing the bootloader is not always something that is achievable
> > for one reason or another
>
> Bootloader also does not use mainline DTS, so where is exactly the problem?
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-03-26 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 0:15 [PATCH 1/2] arm64: dts: Add basic NanoPi R6S (RK3588S) Support Shane Francis
2023-03-26 0:15 ` [PATCH 2/2] dt-bindings: clock: update rk3588 clock definitions Shane Francis
2023-03-26 0:53 ` Heiko Stübner
2023-03-26 12:30 ` Shane Francis
2023-03-26 12:50 ` Peter Geis
2023-03-26 9:37 ` Krzysztof Kozlowski
2023-03-26 12:15 ` Shane Francis
[not found] ` <CABnpCuCzdbWTTp1Gc6wWPsB80J5GYw1QzKtZzzyEYU456E=1JA@mail.gmail.com>
2023-03-26 14:51 ` Krzysztof Kozlowski
2023-03-26 16:57 ` Shane Francis
2023-03-26 16:59 ` Shane Francis
2023-03-26 17:23 ` Krzysztof Kozlowski
2023-03-26 17:51 ` Shane Francis [this message]
2023-03-26 20:02 ` Krzysztof Kozlowski
2023-03-26 21:42 ` Mark Kettenis
2023-03-26 23:40 ` Shane Francis
2023-03-27 9:07 ` Heiko Stübner
2023-03-27 9:22 ` Shane Francis
2023-03-26 9:38 ` [PATCH 1/2] arm64: dts: Add basic NanoPi R6S (RK3588S) Support Krzysztof Kozlowski
2023-03-26 12:31 ` Shane Francis
2023-03-26 18:40 ` [PATCH v2 1/3] " Shane Francis
2023-03-26 18:40 ` [PATCH v2 2/3] dt-bindings: clock: update rk3588 clock definitions Shane Francis
2023-03-26 20:04 ` Krzysztof Kozlowski
2023-03-26 23:31 ` Shane Francis
2023-03-26 18:40 ` [PATCH v2 3/3] arm64: dts: Add FriendlyElec NanoPi R6S device binding Shane Francis
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='CABnpCuA7V9ti6BOoz+3Mq-f=PwgxL2K7rOhjo6tJ4QquSZbaSA@mail.gmail.com' \
--to=bigbeeshane@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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).