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  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]
Date:   Fri, 31 Aug 2018 23:39:20 +0900
From:   Masahiro Yamada <>
To:     Wolfram Sang <>
        Wolfram Sang <>,
        Linux Kernel Mailing List <>
Subject: Re: [Question] When should a driver issue STOP condition?

Hi Wolfram,

2018-08-31 18:53 GMT+09:00 Wolfram Sang <>:
>> The problem is, my driver is forcibly setting
>> STOP condition unless the next message is read.
> This likely is a problem.

Oh, my drivers were wrong from the beginning.

I've sent patches.

> In Linux I2C terminology, a transfer is everything between a START and a
> STOP. A transfer may consist of multiple messages, connected with
> REP_START [1].
> So, a STOP should be generated after the last message of a transfer or
> of I2C_M_STOP is set in a message.

I see.
I hope this is documented somewhere if it has not been yet.

> The latter should be super-rare
> because mostly you should be able to use multiple transfers with a
> regular STOP instead.
> [1] Slide 8 illustrates this:


I should follow "When to not use bus recovery" check-list.


Best Regards
Masahiro Yamada

Powered by blists - more mailing lists