From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-iio@vger.kernel.org,
joshua.yeong@starfivetech.com, devicetree@vger.kernel.org,
linux@roeck-us.net, "Carlos Song" <carlos.song@nxp.com>
Subject: Re: [PATCH v9 4/6] i3c: master: svc: Add basic HDR mode support
Date: Mon, 3 Nov 2025 10:03:39 +0200 [thread overview]
Message-ID: <aQhh2zZVxh1oVuJz@smile.fi.intel.com> (raw)
In-Reply-To: <20251031-i3c_ddr-v9-4-f1e523ebaf78@nxp.com>
On Fri, Oct 31, 2025 at 12:39:16PM -0400, Frank Li wrote:
> Add basic HDR mode support for the svs I3C master driver.
>
> Only support for private transfers and does not support sending CCC
> commands in HDR mode.
>
> Key differences:
> - HDR uses commands (0x00-0x7F for write, 0x80-0xFF for read) to
> distinguish transfer direction.
> - HDR read/write commands must be written to FIFO before issuing the I3C
> address command. The hardware automatically sends the standard CCC command
> to enter HDR mode.
> - HDR exit pattern must be sent instead of send a stop after transfer
> completion.
> - Read/write data size must be an even number.
...
> static bool svc_cmd_is_read(u32 rnw_cmd, u32 type)
> {
> - return rnw_cmd;
> + return (type == SVC_I3C_MCTRL_TYPE_DDR) ? !!(rnw_cmd & 0x80) : rnw_cmd;
This seems confusing. Either !! is redundant (which is actually the case) or
I don't know what the idea behind this.
> +}
...
> +static void svc_i3c_master_emit_force_exit(struct svc_i3c_master *master)
> +{
> + u32 reg;
> +
> + writel(SVC_I3C_MCTRL_REQUEST_FORCE_EXIT, master->regs + SVC_I3C_MCTRL);
> +
> + /*
> + * Not need check error here because it is never happen at hardware. IP
If you move 'IP' to the next line it will be better to read.
> + * just wait for few fclk cycle to complete DDR exit pattern. Even
> + * though fclk stop, timeout happen here, the whole data actually
> + * already finish transfer. The next command will be timeout because
> + * wrong hardware state.
> + */
> + readl_poll_timeout_atomic(master->regs + SVC_I3C_MSTATUS, reg,
> + SVC_I3C_MSTATUS_MCTRLDONE(reg), 0, 1000);
> +
> + /*
> + * This delay is necessary after the emission of a stop, otherwise eg.
> + * repeating IBIs do not get detected. There is a note in the manual
> + * about it, stating that the stop condition might not be settled
> + * correctly if a start condition follows too rapidly.
> + */
> + udelay(1);
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-03 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:39 [PATCH v9 0/6] i3c: Add basic HDR mode support Frank Li
2025-10-31 16:39 ` [PATCH v9 1/6] i3c: Add HDR API support Frank Li
2025-10-31 16:39 ` [PATCH v9 2/6] i3c: Switch to use new i3c_xfer from i3c_priv_xfer Frank Li
2025-10-31 16:39 ` [PATCH v9 3/6] i3c: master: svc: Replace bool rnw with union for HDR support Frank Li
2025-10-31 16:39 ` [PATCH v9 4/6] i3c: master: svc: Add basic HDR mode support Frank Li
2025-11-03 8:03 ` Andy Shevchenko [this message]
2025-10-31 16:39 ` [PATCH v9 5/6] dt-bindings: trivial-devices: add MEMSIC 3-axis magnetometer Frank Li
2025-10-31 16:39 ` [PATCH v9 6/6] iio: magnetometer: Add mmc5633 sensor Frank Li
2025-11-03 8:13 ` Andy Shevchenko
2025-11-03 15:57 ` Frank Li
2025-11-03 18:10 ` Andy Shevchenko
2025-11-01 16:25 ` [PATCH v9 0/6] i3c: Add basic HDR mode support Jonathan Cameron
2025-11-03 8:15 ` Andy Shevchenko
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=aQhh2zZVxh1oVuJz@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=imx@lists.linux.dev \
--cc=jic23@kernel.org \
--cc=joshua.yeong@starfivetech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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