From: Heiko Stuebner <heiko@sntech.de>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: Ondrej Jirman <megi@xff.cz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/7] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi
Date: Tue, 31 Dec 2024 01:27:05 +0100 [thread overview]
Message-ID: <868000342.0ifERbkFSE@phil> (raw)
In-Reply-To: <CALWfF7Kg9HQoqyEYaj9FGPYu3+vAzZNLMVhSr_90SFDg5Syc9w@mail.gmail.com>
Hi Jimmy,
Am Sonntag, 29. Dezember 2024, 20:20:59 CET schrieb Jimmy Hon:
> On Sun, Dec 29, 2024 at 12:44 PM Jimmy Hon <honyuenkwun@gmail.com> wrote:
> >
> > for Orange Pi 5 Plus/Max/Ultra and AI Max
> > ---
> > .../dts/rockchip/rk3588-orangepi-5-plus.dts | 833 ++----------------
> > ...gepi-5-plus.dts => rk3588-orangepi-5.dtsi} | 195 +---
> > 2 files changed, 77 insertions(+), 951 deletions(-)
> > copy arch/arm64/boot/dts/rockchip/{rk3588-orangepi-5-plus.dts => rk3588-orangepi-5.dtsi} (80%)
>
> Heiko,
>
> Should I go ahead and make a v5 including the following in my baseline
> before the refactor?
> - GPU power doman dependency [1]
> - USB 3.0 on 5 Plus [2]
> Do those series look like they'll go in as is?
If you want to do a v5, you _could_ include te USB thing, because that
is DTS only, so on my turf ;-) .
You could also drop the RFC + UNTESTED parts for now and resubmit them
later.
For the GPU power domain I cannot say when this will go in, so better
not depend on it. Especially as we don't know when people will return
from xmas/new-year vacations.
So ideally for the power-domain thing, create a follow-up patch.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: Ondrej Jirman <megi@xff.cz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/7] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi
Date: Tue, 31 Dec 2024 01:27:05 +0100 [thread overview]
Message-ID: <868000342.0ifERbkFSE@phil> (raw)
In-Reply-To: <CALWfF7Kg9HQoqyEYaj9FGPYu3+vAzZNLMVhSr_90SFDg5Syc9w@mail.gmail.com>
Hi Jimmy,
Am Sonntag, 29. Dezember 2024, 20:20:59 CET schrieb Jimmy Hon:
> On Sun, Dec 29, 2024 at 12:44 PM Jimmy Hon <honyuenkwun@gmail.com> wrote:
> >
> > for Orange Pi 5 Plus/Max/Ultra and AI Max
> > ---
> > .../dts/rockchip/rk3588-orangepi-5-plus.dts | 833 ++----------------
> > ...gepi-5-plus.dts => rk3588-orangepi-5.dtsi} | 195 +---
> > 2 files changed, 77 insertions(+), 951 deletions(-)
> > copy arch/arm64/boot/dts/rockchip/{rk3588-orangepi-5-plus.dts => rk3588-orangepi-5.dtsi} (80%)
>
> Heiko,
>
> Should I go ahead and make a v5 including the following in my baseline
> before the refactor?
> - GPU power doman dependency [1]
> - USB 3.0 on 5 Plus [2]
> Do those series look like they'll go in as is?
If you want to do a v5, you _could_ include te USB thing, because that
is DTS only, so on my turf ;-) .
You could also drop the RFC + UNTESTED parts for now and resubmit them
later.
For the GPU power domain I cannot say when this will go in, so better
not depend on it. Especially as we don't know when people will return
from xmas/new-year vacations.
So ideally for the power-domain thing, create a follow-up patch.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-31 0:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 18:41 [PATCH v4 0/7] arm64: dts: rockchip: Orange Pi 5 Max board Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 18:41 ` [PATCH 1/7] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 19:20 ` Jimmy Hon
2024-12-29 19:20 ` Jimmy Hon
2024-12-31 0:27 ` Heiko Stuebner [this message]
2024-12-31 0:27 ` Heiko Stuebner
2024-12-29 18:41 ` [PATCH 2/7] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Max Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 18:41 ` [PATCH 3/7] arm64: dts: rockchip: Add Orange Pi 5 Max board Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 18:41 ` [RFC 4/7] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Ultra Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2025-01-02 21:53 ` Rob Herring
2025-01-02 21:53 ` Rob Herring
2025-01-03 0:18 ` Jimmy Hon
2025-01-03 0:18 ` Jimmy Hon
2024-12-29 18:41 ` [RFC 5/7] arm64: dts: rockchip: Add Orange Pi 5 Ultra board Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 19:06 ` Jimmy Hon
2024-12-29 19:06 ` Jimmy Hon
2024-12-29 18:41 ` [PATCH 6/7] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Max Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-29 19:12 ` Jimmy Hon
2024-12-29 19:12 ` Jimmy Hon
2024-12-30 3:04 ` kernel test robot
2024-12-30 3:04 ` kernel test robot
2025-01-04 7:23 ` kernel test robot
2025-01-04 7:23 ` kernel test robot
2024-12-29 18:41 ` [PATCH UNTESTED 7/7] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Plus Jimmy Hon
2024-12-29 18:41 ` Jimmy Hon
2024-12-30 5:07 ` kernel test robot
2024-12-30 5:07 ` kernel test robot
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=868000342.0ifERbkFSE@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=honyuenkwun@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=megi@xff.cz \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.