Re: [PATCH v2] w1: ds2408: reset on output_write retry with readback

Hi Greg, Exactly as Jean-Francois stated: > Mariusz can chime in but I believe although it was the same exercise > that led to his discoveries, each patch can stand alone and be applied > in any order. > > I will send a v3 without a reply-to-id. Mariusz' patch "[PATCH v2] w1: > fix the resume com

Re: [PATCH v2] w1: ds2408: reset on output_write retry with readback

** resending to list only because of bounce ** Hi Greg, > On Mar 27, 2019, at 12:53, Greg Kroah-Hartman wrote: > > On Thu, Mar 21, 2019 at 11:18:27AM -0400, Jean-Francois Dagenais wrote: >> Originally >> Reported-by: Mariusz Bialonczyk > > That needs to go down in the signed-off-by area. No

Re: [PATCH v2] w1: ds2408: reset on output_write retry with readback

On Thu, Mar 21, 2019 at 11:18:27AM -0400, Jean-Francois Dagenais wrote: > Originally > Reported-by: Mariusz Bialonczyk That needs to go down in the signed-off-by area. Also, please resend this series in a way that I can apply it. You didn't say what the order was for the v2 patches. thanks, g

[PATCH v2] w1: ds2408: reset on output_write retry with readback

Originally Reported-by: Mariusz Bialonczyk When we have success in 'Channel Access Write' but reading back latch states fails, a write is retried without doing a proper slave reset. This leads to protocol errors as the slave treats the next 'Channel Access Write' as the continuation of previous c