linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI
Date: Tue, 08 Nov 2016 16:50:24 -0800	[thread overview]
Message-ID: <57268103e8fabf344723eae99b45ec7d@agner.ch> (raw)
In-Reply-To: <20161108173315.GA16082@Sanchayan-Arch.localdomain>

On 2016-11-08 09:33, maitysanchayan at gmail.com wrote:
> Hello Shawn,
> 
> On 16-10-22 15:43:04, Vladimir Zapolskiy wrote:
>> Hi Shawn,
>>
>> On 10/22/2016 06:25 AM, Shawn Guo wrote:
>> > On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote:
>> > > Remove the use of DDC I2C bus bitbang to support reading of EDID
>> > > and rely on support from internal HDMI I2C master controller instead.
>> > > As a result remove the device tree property ddc-i2c-bus.
>> > >
>> > > Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
>> >
>> > I think that the dw-hdmi i2c support [1] is a prerequisite of this
>> > patch.  I do not see it lands on v4.9-rc1.  Or am I missing something?
>> >
>> > Shawn
>> >
>> > [1] https://patchwork.kernel.org/patch/9296883/
>> >
>>
>> I'm adding Philipp to Cc, since he is the last one who tested the change
>> and helped me to push the change to the mainline:
>>
>>   https://lists.freedesktop.org/archives/dri-devel/2016-September/118569.html
>>
>> The problem is that there is no official DW HDMI bridge maintainer, may be
>> you can review the change, and if you find it satisfactory push it through
>> ARM/iMX tree.
> 
> Shawn, is it okay if that patch goes through your ARM/iMX tree?

I don't think it makes sense that the DRM bridge changes go through
Shawn's tree. Dave should merge Philipps pull request...

--
Stefan

  reply	other threads:[~2016-11-09  0:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  5:11 [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI Sanchayan Maity
2016-09-19  5:11 ` [PATCH v2 2/3] ARM: dts: imx6q-apalis-ixora: Remove use of pwm-leds Sanchayan Maity
2016-10-22  3:32   ` Shawn Guo
2016-09-19  5:11 ` [PATCH v2 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight Sanchayan Maity
2016-10-22  3:32   ` Shawn Guo
2016-09-27  4:19 ` [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI maitysanchayan at gmail.com
2016-09-27  6:28 ` Marcel Ziswiler
2016-10-22  3:25 ` Shawn Guo
2016-10-22 12:43   ` Vladimir Zapolskiy
2016-11-08 17:33     ` maitysanchayan at gmail.com
2016-11-09  0:50       ` Stefan Agner [this message]
2016-11-10 18:29         ` Vladimir Zapolskiy
2016-11-11  4:27           ` Stefan Agner
2016-11-14  1:55             ` Shawn Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57268103e8fabf344723eae99b45ec7d@agner.ch \
    --to=stefan@agner.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).