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: <ad5375b6-5a1b-4c04-a4d9-c99fb0afaeb8@linux.intel.com>
Date: Thu, 14 Nov 2024 17:22:40 +0200
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Billy Tsai <billy_tsai@...eedtech.com>, alexandre.belloni@...tlin.com,
 Shyam-sundar.S-k@....com, Guruvendra.Punugupati@....com,
 krishnamoorthi.m@....com, linux-i3c@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] i3c: mipi-i3c-hci: Support SETDASA CCC

On 11/13/24 5:58 AM, Billy Tsai wrote:
> When the I3C subsystem wants to assign a dynamic address using the SETDASA
> CCC, it needs to attach the I3C device with device info that includes only
> the static address. In the HCI, if the driver want to send this SETDASA
> CCC, a DAT entry is required to temporarily fill the device's static
> address into the dynamic address field. Afterward, the reattach API will
> be executed to update the DAT with the correct dynamic addrees value.
> 
> Signed-off-by: Billy Tsai <billy_tsai@...eedtech.com>
> ---
>   drivers/i3c/master/mipi-i3c-hci/core.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
(Minor comment to the subject. Is this rather fix than support SETDASA?)

Reviewed-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ