From: "Heiko Stübner" <heiko@sntech.de>
To: Chris Morgan <macroalpha82@gmail.com>, Dragan Simic <dsimic@manjaro.org>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh@kernel.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 0/4] User Requested Fixes for Powkiddy RK3566 Devices
Date: Mon, 25 Mar 2024 22:53:02 +0100 [thread overview]
Message-ID: <2854897.88bMQJbFj6@diego> (raw)
In-Reply-To: <5e2f0da3fc066cf1faddda71bb6ea2e7@manjaro.org>
Am Montag, 25. März 2024, 18:57:06 CET schrieb Dragan Simic:
> Hello Chris,
>
> On 2024-03-25 18:51, Chris Morgan wrote:
> > From: Chris Morgan <macromorgan@hotmail.com>
> >
> > Users have requested fixes for Powkiddy devices to help with some
> > intermittent WiFi issues by adding additional properties to the
> > SDMMC2 node. They have also requested that the model name be
> > represented consistently with both the manufacturer name and model
> > name. Lastly, there exists a second configuration of the RGB30 with
> > a slightly different regulator layout we need to describe.
> >
> > I have added the new/additional property of "chasis-type" as well.
>
> Shouldn't this series be labeled as v2?
I think this is for Powkiddy handhelds, the other series was
for Anberic ones.
Somehow they design and build seemingly dozens of somewhat
similar handhelds around the rk3566 ;-)
> By the way, regarding renaming the mmcX aliases, maybe that would
> actually be doable, but only if you have full control over software
> that runs on these devices.
>
> > Chris Morgan (4):
> > dts: rockchip: Add chasis-type for Powkiddy rk3566 devices
> > arm64: dts: rockchip: Update sdmmc node for wifi on powkiddy rk3566
> > arm64: dts: rockchip: Correct model name for Powkiddy RK3566 Devices
> > arm64: dts: rockchip: Describe Alternate Regulator Config on RGB30
> >
> > .../dts/rockchip/rk3566-powkiddy-rgb30.dts | 30 ++++++++++++++++++-
> > .../dts/rockchip/rk3566-powkiddy-rk2023.dts | 6 +++-
> > .../dts/rockchip/rk3566-powkiddy-rk2023.dtsi | 4 +++
> > .../boot/dts/rockchip/rk3566-powkiddy-x55.dts | 4 +++
> > 4 files changed, 42 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2024-03-25 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:51 [PATCH 0/4] User Requested Fixes for Powkiddy RK3566 Devices Chris Morgan
2024-03-25 17:51 ` [PATCH 1/4] dts: rockchip: Add chasis-type for Powkiddy rk3566 devices Chris Morgan
2024-03-25 17:51 ` [PATCH 2/4] arm64: dts: rockchip: Update sdmmc node for wifi on powkiddy rk3566 Chris Morgan
2024-03-25 17:51 ` [PATCH 3/4] arm64: dts: rockchip: Correct model name for Powkiddy RK3566 Devices Chris Morgan
2024-03-25 17:51 ` [PATCH 4/4] arm64: dts: rockchip: Describe Alternate Regulator Config on RGB30 Chris Morgan
2024-04-11 18:42 ` Heiko Stuebner
2024-03-25 17:57 ` [PATCH 0/4] User Requested Fixes for Powkiddy RK3566 Devices Dragan Simic
2024-03-25 21:53 ` Heiko Stübner [this message]
2024-03-25 21:58 ` Dragan Simic
2024-03-25 22:10 ` Chris Morgan
2024-04-11 18:29 ` (subset) " Heiko Stuebner
2024-04-12 14:35 ` Chris Morgan
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=2854897.88bMQJbFj6@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--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 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).