linux-kernel - Re: [PATCH] i3c: dw: Fix IBI intr signal programming

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] [thread-next>] [day] [month] [year] [list]

Date: Fri, 7 Jun 2024 11:41:34 +0530
From: "Aniket ." <aniketmaurya@...gle.com>
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>, Joel Stanley <joel@....id.au>, 
	Billy Tsai <billy_tsai@...eedtech.com>, linux-i3c@...ts.infradead.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i3c: dw: Fix IBI intr signal programming

Hi Jeremy,

> This is more for handling IP configuration options we may see in future.
> For example, I believe support for target/secondary mode is entirely
> optional too.

I was hoping to add support for target/secondary master, we might have
different drivers instead, something like what's done for i2c-dw drivers. But
that's a thought for another day.

> I think keeping the mask value locally would be best. this means we
>
>  1) cannot get the counter and mask out of sync; and
>  2) don't need to do a read-modify-write on a register that is only
>     updated by the driver.

Sure, let me make the patch.

Thanks,
Aniket