From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Rob Herring <robh+dt@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Magnus Damm <magnus.damm@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/5] renesas,iic: Fixes and DT binding to json-schema conversion
Date: Fri, 18 Jun 2021 13:04:06 +0200 [thread overview]
Message-ID: <cover.1624013644.git.geert+renesas@glider.be> (raw)
Hi all,
According to the Hardware User's Manual, automatic transmission for PMIC
control (DVFS) is not available on RZ/G1, R-Car E3, and RZ/G2E SoC.
Thanks to various experiments by Wolfram (thanks a lot!) and me, we
devised this really means that support for automatic DVFS is not
present, while the IIC automatic transmission feature itself is still
available, albeit not super useful.
Hence this patch series updates the renesas,iic DT bindings and DTS
files to always consider all variants and instances compatible with the
family-specific and generic versions, and converts the bindings to
json-schema.
Changes compared to v1[1][2]:
- Consider all variants and instances compatible with the
family-specific and generic versions.
I plan to queue patches 2-4 in renesas-devel for v5.15.
Thanks for your comments!
[1] "[PATCH/RFC 4/6] dt-bindings: i2c: renesas,iic: Convert to json-schema"
https://lore.kernel.org/r/ecfaf6be5e8c285db2bcc823bb1dd89931fa5c29.1620138454.git.geert+renesas@glider.be
[2] "[PATCH 0/2] ARM: dts: r8a7745,r8a7794: Remove generic compatible
strings from iic blocks"
https://lore.kernel.org/r/cover.1620139307.git.geert+renesas@glider.be
Geert Uytterhoeven (5):
dt-bindings: i2c: renesas,iic: Always declare generic compatibility
ARM: dts: rzg1: Add generic compatible strings to IIC nodes
arm64: dts: renesas: r8a774c0: Add generic compatible string to IIC
node
arm64: dts: renesas: r8a77990: Add generic compatible string to IIC
node
dt-bindings: i2c: renesas,iic: Convert to json-schema
.../devicetree/bindings/i2c/renesas,iic.txt | 72 ---------
.../bindings/i2c/renesas,rmobile-iic.yaml | 149 ++++++++++++++++++
MAINTAINERS | 2 +-
arch/arm/boot/dts/r8a7742.dtsi | 4 +-
arch/arm/boot/dts/r8a7743.dtsi | 4 +-
arch/arm/boot/dts/r8a7744.dtsi | 4 +-
arch/arm64/boot/dts/renesas/r8a774c0.dtsi | 6 +-
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 6 +-
8 files changed, 167 insertions(+), 80 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/i2c/renesas,iic.txt
create mode 100644 Documentation/devicetree/bindings/i2c/renesas,rmobile-iic.yaml
--
2.25.1
next reply other threads:[~2021-06-18 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 11:04 Geert Uytterhoeven [this message]
2021-06-18 18:43 ` [PATCH v2 0/5] renesas,iic: Fixes and DT binding to json-schema conversion Wolfram Sang
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=cover.1624013644.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).