Re: [PATCH 0/9] i2c: rcar: tackle race conditions in the driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Wolfram,

On Sat, Sep 5, 2015 at 4:31 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
> On Fri, Sep 04, 2015 at 01:33:39PM +0900, Magnus Damm wrote:
>> Hi Wolfram,
>>
>> On Fri, Sep 4, 2015 at 5:40 AM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
>> >
>> >> > So I refactored the driver to setup new messages in interrupt context, too.
>> >> > This avoids the race for b) because we are now setting up the new message
>> >> > before we release the i2c bus clock (before we released the clock and set up
>> >> > the message in process context).
>> >>
>> >> Could this fix the HDMI EDID read issue on Koelsch ?
>> >
>> > I surely hope so. I can't test because I don't have Koelsch.
>>
>> FYI, I have enabled Koelsch remote access on port 8001 if you want to
>> give it a shot!
>
> Thanks! Is there a HDMI monitor connected?

Yes, now a HD-ready TV is hooked up. It should give you something over
EDID. Let me know when you're done and I'll move things back.

Cheers,

/ magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux