From: Prabhakar <prabhakar.csengg@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Brandt <chris.brandt@renesas.com>,
Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH v3 0/4] Add RIIC support for Renesas RZ/V2H SoC
Date: Tue, 19 Mar 2024 13:24:59 +0000 [thread overview]
Message-ID: <20240319132503.80628-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi all,
This patch series aims to add RIIC support for Renesas RZ/V2H(P) SoC.
v2->v3
- Included RB tags
- For riic_writeb() now passing val as second argument and
offset as third argument
v1->v2
- Dropped dt binding which update the comment.
- Used a const for V2H SoC instead of enum in items list
- Dropped internal review tags
- Renamed i2c read/write to riic_readb/riic_writeb
- Made riic as first parameter for riic_writeb
- Dropped family from struct riic_of_data
- Included RIIC_REG_END in enum list as flexible array member
in a struct with no named members is not allowed
Cheers,
Prabhakar
Lad Prabhakar (4):
dt-bindings: i2c: renesas,riic: Document R9A09G057 support
i2c: riic: Introduce helper functions for I2C read/write operations
i2c: riic: Pass register offsets and chip details as OF data
i2c: riic: Add support for R9A09G057 SoC
.../devicetree/bindings/i2c/renesas,riic.yaml | 19 +--
drivers/i2c/busses/i2c-riic.c | 125 +++++++++++++-----
2 files changed, 100 insertions(+), 44 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-19 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 13:24 Prabhakar [this message]
2024-03-19 13:25 ` [PATCH v3 1/4] dt-bindings: i2c: renesas,riic: Document R9A09G057 support Prabhakar
2024-03-20 9:30 ` Wolfram Sang
2024-03-19 13:25 ` [PATCH v3 2/4] i2c: riic: Introduce helper functions for I2C read/write operations Prabhakar
2024-03-19 13:32 ` Geert Uytterhoeven
2024-03-20 10:04 ` Wolfram Sang
2024-03-19 13:25 ` [PATCH v3 3/4] i2c: riic: Pass register offsets and chip details as OF data Prabhakar
2024-03-20 10:05 ` Wolfram Sang
2024-03-19 13:25 ` [PATCH v3 4/4] i2c: riic: Add support for R9A09G057 SoC Prabhakar
2024-03-20 10:06 ` Wolfram Sang
2024-03-21 21:11 ` [PATCH v3 0/4] Add RIIC support for Renesas RZ/V2H SoC Andi Shyti
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=20240319132503.80628-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.csengg@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=chris.brandt@renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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 read-only IMAP folder(s) and NNTP newsgroup(s).