From: Johan Jonker <jbx6244@gmail.com>
To: kever.yang@rock-chips.com
Cc: sjg@chromium.org, philipp.tomsich@vrull.eu, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de,
ulf.hansson@linaro.org, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, kishon@ti.com, vkoul@kernel.org,
thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de,
gregkh@linuxfoundation.org, broonie@kernel.org,
wim@linux-watchdog.org, linux@roeck-us.net,
zhangqing@rock-chips.com, jamie@jamieiles.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-phy@lists.infradead.org,
linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org,
linux-spi@vger.kernel.org, linux-usb@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: [PATCH v1 00/11] Add more Rockchip rk3128 compatible strings
Date: Sat, 10 Sep 2022 00:01:00 +0200 [thread overview]
Message-ID: <3ed145c6-f400-ee75-ccac-894b0a0d15d2@gmail.com> (raw)
Mainline U-boot has some support for legacy Rockchip SoC rk3128.
The rk3128.dtsi file is in need for some upgrading.
To verify the nodes more Rockchip rk3128 compatible strings are needed.
Not tested with hardware.
No intent to port drivers or dts files to Linux for now without physical board.
So pure for the bindings.
https://lore.kernel.org/u-boot/421195e1-472c-f337-e87a-b0b6d520b808@gmail.com/T/#u
Johan Jonker (11):
dt-bindings: serial: rockchip: add rockchip,rk3128-uart
dt-bindings: i2c: rockchip: add rockchip,rk3128-i2c
dt-bindings: pwm: rockchip: add rockchip,rk3128-pwm
dt-bindings: mmc: rockchip: add rockchip,rk3128-dw-mshc
dt-bindings: spi: rockchip: add rockchip,rk3128-spi
dt-bindings: usb: dwc2: rockchip: add rockchip,rk3128-usb
dt-bindings: watchdog: rockchip: add rockchip,rk3128-wdt
dt-bindings: arm: rockchip: pmu: add rockchip,rk3128-pmu
dt-bindings: phy: phy-rockchip-inno-usb2: add rockchip,rk3128-usb2phy
dt-bindings: soc: rockchip: grf: add rockchip,rk3128-grf
dt-bindings: mtd: rockchip: add rockchip,rk3128-nfc
Documentation/devicetree/bindings/arm/rockchip/pmu.yaml | 2 ++
Documentation/devicetree/bindings/i2c/i2c-rk3x.yaml | 1 +
Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.yaml | 1 +
.../devicetree/bindings/mtd/rockchip,nand-controller.yaml | 4 +++-
.../devicetree/bindings/phy/phy-rockchip-inno-usb2.yaml | 1 +
Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
.../devicetree/bindings/serial/snps-dw-apb-uart.yaml | 1 +
Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 2 ++
Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
Documentation/devicetree/bindings/usb/dwc2.yaml | 1 +
Documentation/devicetree/bindings/watchdog/snps,dw-wdt.yaml | 1 +
11 files changed, 15 insertions(+), 1 deletion(-)
--
2.20.1
reply other threads:[~2022-09-09 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ed145c6-f400-ee75-ccac-894b0a0d15d2@gmail.com \
--to=jbx6244@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=jamie@jamieiles.com \
--cc=kever.yang@rock-chips.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.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-mtd@lists.infradead.org \
--cc=linux-phy@lists.infradead.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=miquel.raynal@bootlin.com \
--cc=philipp.tomsich@vrull.eu \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=sjg@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=wim@linux-watchdog.org \
--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;
as well as URLs for NNTP newsgroup(s).