linux-kernel - Re: [PATCH v1] i3c/master: cmd_v1: Fix the rule for getting i3c mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <172563708354.975422.17313525144371866545.b4-ty@bootlin.com>
Date: Fri, 6 Sep 2024 17:38:41 +0200
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: jarkko.nikula@...ux.intel.com, linux-i3c@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	Billy Tsai <billy_tsai@...eedtech.com>
Subject: Re: [PATCH v1] i3c/master: cmd_v1: Fix the rule for getting i3c mode

On Mon, 26 Aug 2024 11:38:21 +0800, Billy Tsai wrote:
> Based on the I3C TCRI specification, the rules for determining the I3C
> mode are as follows:
> I3C SCL rate > 8MHz: use SDR0, with a maximum data rate of 8MHz
> I3C SCL rate > 6MHz: use SDR1, with a maximum data rate of 6MHz
> I3C SCL rate > 4MHz: use SDR2, with a maximum data rate of 4MHz
> I3C SCL rate > 2MHz: use SDR3, with a maximum data rate of 2MHz
> Otherwise, use SDR4
> 
> [...]

Applied, after fixing the commit log

[1/1] i3c/master: cmd_v1: Fix the rule for getting i3c mode
      https://git.kernel.org/abelloni/c/061dd21ca712

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com