From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Frank Li <Frank.Li@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i3c@lists.infradead.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v5 4/4] i3c: master: Add basic driver for the Renesas I3C controller
Date: Wed, 30 Jul 2025 16:54:08 +0200 [thread overview]
Message-ID: <aIoyEKpB7twvKDGN@shikoro> (raw)
In-Reply-To: <CAMuHMdX5BfNm1GJ8UyqftcVc07p1aodXuVHxNaYWDYLHaxzXMw@mail.gmail.com>
> Why not use readl() and writel() directly?
> To make it easier to add debug prints during initial development?
Yes. And ultimately, there is a patch in the works converting the driver
to MMIO regmap to get rid of _all_ the helpers. I couldn't make this in
time for the 6.17 mergewindow, though, because of... gory details.
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-07-30 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:41 [PATCH v5 0/4] i3c: add support for the Renesas controller Wolfram Sang
2025-07-24 9:41 ` [PATCH v5 1/4] i3c: Standardize defines for specification parameters Wolfram Sang
2025-07-24 9:41 ` [PATCH v5 2/4] i3c: Add more parameters for controllers to the header Wolfram Sang
2025-07-25 13:47 ` Frank Li
2025-07-24 9:41 ` [PATCH v5 3/4] dt-bindings: i3c: Add Renesas I3C controller Wolfram Sang
2025-07-24 9:41 ` [PATCH v5 4/4] i3c: master: Add basic driver for the " Wolfram Sang
2025-07-30 14:39 ` Geert Uytterhoeven
2025-07-30 14:54 ` Wolfram Sang [this message]
2025-07-30 23:40 ` [PATCH v5 0/4] i3c: add support for the Renesas controller Alexandre Belloni
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=aIoyEKpB7twvKDGN@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=geert@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=tommaso.merciai.xr@bp.renesas.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