mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: John Stultz <john.stultz@linaro.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/5 v3] adv7511 EDID probing improvements
Date: Thu, 12 Jan 2017 09:52:41 +0530	[thread overview]
Message-ID: <f7b94c6e-1e13-32f6-4ff7-d8c9d34c3ec0@codeaurora.org> (raw)
In-Reply-To: <CALAqxLVEyYbxQe8_O+9hAe9B0NYnXy-Oy04nxroHezidFSQjig@mail.gmail.com>



On 01/12/2017 05:36 AM, John Stultz wrote:
> On Wed, Jan 11, 2017 at 12:48 AM, Archit Taneja <architt@codeaurora.org> wrote:
>> Hi,
>>
>> On 01/04/2017 01:11 AM, John Stultz wrote:
>>>
>>> Hope everyone had a good newyears!
>>>
>>> Wanted to re-send out v3 of this patch set improving the EDID
>>> probing on the adv7511 used on HiKey, for consideration for
>>> merging for 4.11
>>>
>>> The first three patches are fixups that are hopefully straight
>>> forward, integrating feedback I got from Laurant.
>>>
>>> The last two patches try to clean up and resue code, which as
>>> a side effect avoids an issue I'm seeing where something is
>>> going wrong with the regmap cache state for the
>>> ADV7511_REG_EDID_I2C_ADDR(0x43) register which results in
>>> i2c_transfer errors if we don't do the
>>> regcache_sync/_mark_dirty() calls. I suspect there might be a
>>> better solution there, but have not gotten any other suggestions
>>> so I wanted to go ahead and submit these.
>>>
>>> Thoughts and feedback would be appreciated!
>>
>>
>> Tested on DB410c on 4.10-rc3. Works well for me.
>
> Archit: Thanks for the testing! Is there anything else you need from
> me (or others) to queue this for 4.11? Or should I be submitting it to
> someone else?

A final Ack/Test from Laurent for ADV7511 would be nice. I'll be the one
queuing it to drm-misc for 4.11.

Thanks,
Archit


>
> thanks
> -john
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-01-12  4:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 19:41 John Stultz
2017-01-03 19:41 ` [PATCH 1/5 v3] drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq context John Stultz
2017-01-03 19:41 ` [PATCH 2/5 v3] drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event() John Stultz
2017-01-16 15:47   ` Laurent Pinchart
2017-01-16 15:56     ` Laurent Pinchart
2017-01-16 19:31       ` John Stultz
2017-01-03 19:41 ` [PATCH 3/5 v3] drm/bridge: adv7511: Enable HPD interrupts to support hotplug and improve monitor detection John Stultz
2017-01-03 19:41 ` [PATCH 4/5 v3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally John Stultz
2017-01-16 15:50   ` Laurent Pinchart
2017-01-03 19:41 ` [PATCH 5/5 v3] drm/bridge: adv7511: Reuse __adv7511_power_on/off() when probing EDID John Stultz
2017-01-16 16:03   ` Laurent Pinchart
2017-01-16 20:14     ` John Stultz
2017-01-16 22:25       ` Laurent Pinchart
2017-01-16 23:16         ` [RFC][PATCH] drm/bridge: adv7511: Re-write the i2c address as it may have been lost John Stultz
2017-01-16 23:36           ` Laurent Pinchart
2017-01-16 23:39             ` John Stultz
2017-01-11  8:48 ` [PATCH 0/5 v3] adv7511 EDID probing improvements Archit Taneja
2017-01-12  0:06   ` John Stultz
2017-01-12  4:22     ` Archit Taneja [this message]
2017-01-16 15:57 ` Laurent Pinchart

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=f7b94c6e-1e13-32f6-4ff7-d8c9d34c3ec0@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=john.stultz@linaro.org \
    --cc=lars@metafoo.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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

all inboxes | Powered by JetHome®