On 2018-08-02 08:06, Peter Rosin wrote:
> On 2018-08-01 11:35, Russell King - ARM Linux wrote:
>> On Wed, Aug 01, 2018 at 11:01:12AM +0200, Peter Rosin wrote:
>>> I don't think it's a problem with the atmel I2C driver. IIRC, the
>>> tda998x driver issues the command a initiate the EDID read, but th
On Mon, Nov 12, 2018 at 04:50:37PM +, Peter Rosin wrote:
> On 2018-08-02 08:06, Peter Rosin wrote:
> > On 2018-08-01 11:35, Russell King - ARM Linux wrote:
> >> On Wed, Aug 01, 2018 at 11:01:12AM +0200, Peter Rosin wrote:
> >>> I don't think it's a problem with the atmel I2C driver. IIRC, the
>
On Tue, Jul 31, 2018 at 09:53:57AM +0200, Peter Rosin wrote:
> On 2018-07-31 09:41, Russell King - ARM Linux wrote:
> > On Tue, Jul 31, 2018 at 07:44:24AM +0200, Peter Rosin wrote:
> >> On 2018-07-30 18:41, Russell King - ARM Linux wrote:
> >>> Hi,
> >>>
> >>> This is a re-posting of the series I r
On 2018-07-31 09:41, Russell King - ARM Linux wrote:
> On Tue, Jul 31, 2018 at 07:44:24AM +0200, Peter Rosin wrote:
>> On 2018-07-30 18:41, Russell King - ARM Linux wrote:
>>> Hi,
>>>
>>> This is a re-posting of the series I responded to Peter Rosin's May
>>> posting, with a few bugs fixed, and the
On Wed, Aug 01, 2018 at 11:01:12AM +0200, Peter Rosin wrote:
> I don't think it's a problem with the atmel I2C driver. IIRC, the
> tda998x driver issues the command a initiate the EDID read, but that
> times out. So it appears to be the TDA19988 that fails to read the
> EDID over the DDC bus? Which
On 2018-08-01 11:35, Russell King - ARM Linux wrote:
> On Wed, Aug 01, 2018 at 11:01:12AM +0200, Peter Rosin wrote:
>> I don't think it's a problem with the atmel I2C driver. IIRC, the
>> tda998x driver issues the command a initiate the EDID read, but that
>> times out. So it appears to be the TDA1
On 2018-07-31 13:15, Russell King - ARM Linux wrote:
> On Tue, Jul 31, 2018 at 12:43:34PM +0200, Peter Rosin wrote:
>> On 2018-07-31 11:23, Russell King - ARM Linux wrote:
>>> On Tue, Jul 31, 2018 at 09:53:57AM +0200, Peter Rosin wrote:
On 2018-07-31 09:41, Russell King - ARM Linux wrote:
On Tue, Jul 31, 2018 at 07:44:24AM +0200, Peter Rosin wrote:
> On 2018-07-30 18:41, Russell King - ARM Linux wrote:
> > Hi,
> >
> > This is a re-posting of the series I responded to Peter Rosin's May
> > posting, with a few bugs fixed, and the bridge registered outside of
> > the component helper.
On 2018-07-31 11:23, Russell King - ARM Linux wrote:
> On Tue, Jul 31, 2018 at 09:53:57AM +0200, Peter Rosin wrote:
>> On 2018-07-31 09:41, Russell King - ARM Linux wrote:
>>> On Tue, Jul 31, 2018 at 07:44:24AM +0200, Peter Rosin wrote:
On 2018-07-30 18:41, Russell King - ARM Linux wrote:
On Tue, Jul 31, 2018 at 12:43:34PM +0200, Peter Rosin wrote:
> On 2018-07-31 11:23, Russell King - ARM Linux wrote:
> > On Tue, Jul 31, 2018 at 09:53:57AM +0200, Peter Rosin wrote:
> >> On 2018-07-31 09:41, Russell King - ARM Linux wrote:
> >>> On Tue, Jul 31, 2018 at 07:44:24AM +0200, Peter Rosin
On 2018-07-30 18:41, Russell King - ARM Linux wrote:
> Hi,
>
> This is a re-posting of the series I responded to Peter Rosin's May
> posting, with a few bugs fixed, and the bridge registered outside of
> the component helper. This should allow Peter to use the driver
> while maintaining armada dr
11 matches
Mail list logo