linux-kernel - RE: [PATCH 2/2] i2c: designware: slave should do WRITE_REQUESTED before WRITE

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:   Wed, 4 Nov 2020 10:51:34 +0000
From:   <Michael.Wu@...ics.com>
To:     <wsa@...nel.org>
CC:     <jarkko.nikula@...ux.intel.com>,
        <andriy.shevchenko@...ux.intel.com>,
        <mika.westerberg@...ux.intel.com>, <linux-i2c@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <morgan.chang@...ics.com>
Subject: RE: [PATCH 2/2] i2c: designware: slave should do WRITE_REQUESTED
 before WRITE_RECEIVED

Hi Wolfram,

> Thanks for the detailed explanation! Okay, then what you do looks
> correct to me (from a high level perspective without really knowing the
> HW): when RX is full, you first send the state WRITE_REQUESTED when
> there is no other transfer on-going. Then you send WRITE_RECEIVED
> immediately. I think this is the way to do it.

Bingo!! Thanks for your understanding.

I think I should have a habit of writing comments... X-P

Best regards,
Michael Wu