From: Kever Yang <kever.yang@rock-chips.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: heiko@sntech.de, linux-rockchip@lists.infradead.org,
"Simon Xue" <xxm@rock-chips.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Mark Brown" <broonie@kernel.org>,
"Chris Morgan" <macromorgan@hotmail.com>,
"Frank Wang" <frank.wang@rock-chips.com>,
"Jamie Iles" <jamie@jamieiles.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, "Jonas Karlman" <jonas@kwiboo.se>,
"Johan Jonker" <jbx6244@gmail.com>,
"David Airlie" <airlied@gmail.com>,
dri-devel@lists.freedesktop.org,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
linux-i2c@vger.kernel.org, "Shawn Lin" <shawn.lin@rock-chips.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Elaine Zhang" <zhangqing@rock-chips.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Finley Xiao" <finley.xiao@rock-chips.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"FUKAUMI Naoki" <naoki@radxa.com>,
linux-pwm@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Andy Yan" <andyshrk@163.com>,
linux-serial@vger.kernel.org,
"Michael Riesch" <michael.riesch@wolfvision.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Andi Shyti" <andi.shyti@kernel.org>,
devicetree@vger.kernel.org,
"Diederik de Haas" <didi.debian@cknow.org>,
linux-watchdog@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Lee Jones" <lee@kernel.org>,
"Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
"Shresth Prasad" <shresthprasad7@gmail.com>,
"Tim Lunn" <tim@feathertop.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Jisheng Zhang" <jszhang@kernel.org>,
"Dragan Simic" <dsimic@manjaro.org>,
"Detlev Casanova" <detlev.casanova@collabora.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, linux-usb@vger.kernel.org,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Subject: Re: [PATCH v2 00/17] rockchip: Add rk3562 support
Date: Fri, 10 Jan 2025 15:58:44 +0800 [thread overview]
Message-ID: <3460b2a3-9579-4a12-9eff-6e2f1a1cc91c@rock-chips.com> (raw)
In-Reply-To: <sasnc2ocxnlfp4kprsobu5gkajjb5wdxhld73bg6xocgb3foah@yjmphtvpmyff>
Hi Krzysztof,
Thanks very much for your review.
On 2024/12/27 15:38, Krzysztof Kozlowski wrote:
> On Tue, Dec 24, 2024 at 05:49:03PM +0800, Kever Yang wrote:
>> This patch set adds rk3562 SoC and its evb support.
>>
>> Split out patches belong to different subsystem.
>>
>> Test with GMAC, USB, PCIe, EMMC, SD Card.
>>
>> This patch set is base on the patche set for rk3576 evb1 support.
>>
>> Changes in v2:
>> - Update in sort order
>> - remove grf in cru
>> - Update some properties order
>>
>> Finley Xiao (2):
>> arm64: dts: rockchip: add core dtsi for RK3562 Soc
>> arm64: dts: rockchip: Add RK3562 evb2 devicetree
>>
>> Kever Yang (15):
>> dt-bindings: PCI: dwc: rockchip: Add rk3562 support
>> dt-bindings: mmc: Add support for rk3562 eMMC
>> dt-bindings: mmc: rockchip-dw-mshc: Add rk3562 compatible string
>> dt-bindings: power: rockchip: Add bindings for rk3562
>> dt-bindings: i2c: i2c-rk3x: Add rk3562 compatible
>> dt-bindings: gpu: Add rockchip,rk3562-mali compatible
>> dt-bindings: watchdog: Add rk3562 compatible
>> dt-bindings: spi: Add rockchip,rk3562-spi compatible
>> dt-bindings: serial: snps-dw-apb-uart: Add support for rk3562
>> dt-bindings: usb: dwc3: add compatible for rk3562
>> dt-bindings: pwm: rockchip: Add rockchip,rk3562-pwm
>> dt-bindings: rockchip: pmu: Add rk3562 compatible
>> dt-bindings: soc: rockchip: Add rk3562 syscon compatibles
>> dt-bindings: arm: rockchip: Add rk3562 evb2 board
>> dt-bindings: mfd: syscon: Add rk3562 QoS register compatible
> You squezzed here like 12 different subsystems. Some of these changes
> suggest missing drivers.
I have split out all the patches with driver change as separate patch set.
All the other dt-binding patches in this patchset is re-use the driver
without any change,
but only add a new "rockchip, rk3562-" based compatible entry, and also
no more info
need to explain in the commit message which I usually copy from commit
msg already in tree
and change the soc to rk3562.
I think this patch set will be clear enough for the new soc/board
support. So do you mean
I have to send the 1st~15th of this patchset one by one separately so
that they can reach
to different subsystems? I believe there is no much useful change for
the cc list is provide
by the tool automatically and the commit msg can update as Uwe's
suggestion:
The PWM core on Rockchip's RK3562 is the same as the one already
included in RK3328. Extend the binding accordingly to allow
compatible = "rockchip,rk3562-pwm", "rockchip,rk3328-pwm";
Thanks,
- Kever
>
> Please read basic upstreaming guide, some previous discussions and get
> internal rock-chips help so we want repeat basics over and over.
>
> Bindings are with drivers. Send them to respective subsystems.
>
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2025-01-10 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 9:49 [PATCH v2 00/17] rockchip: Add rk3562 support Kever Yang
2024-12-24 9:49 ` [PATCH v2 05/17] dt-bindings: i2c: i2c-rk3x: Add rk3562 compatible Kever Yang
2024-12-26 0:36 ` Heiko Stuebner
2024-12-27 7:38 ` [PATCH v2 00/17] rockchip: Add rk3562 support Krzysztof Kozlowski
2025-01-10 7:58 ` Kever Yang [this message]
2024-12-27 8:32 ` Krzysztof Kozlowski
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=3460b2a3-9579-4a12-9eff-6e2f1a1cc91c@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=airlied@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=andyshrk@163.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsimic@manjaro.org \
--cc=finley.xiao@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=jamie@jamieiles.com \
--cc=jbx6244@gmail.com \
--cc=jirislaby@kernel.org \
--cc=jonas@kwiboo.se \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kw@linux.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lpieralisi@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macromorgan@hotmail.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=michael.riesch@wolfvision.net \
--cc=mripard@kernel.org \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.com \
--cc=shresthprasad7@gmail.com \
--cc=simona@ffwll.ch \
--cc=tim@feathertop.org \
--cc=tzimmermann@suse.de \
--cc=ukleinek@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wim@linux-watchdog.org \
--cc=xxm@rock-chips.com \
--cc=zhangqing@rock-chips.com \
/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