linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC 01/10] drm: ADV7511 i2c HDMI encoder driver
Date: Mon, 02 Sep 2013 15:09:11 +0000	[thread overview]
Message-ID: <5224AA17.6060806@metafoo.de> (raw)
In-Reply-To: <1377866264-21110-2-git-send-email-ulrich.hecht@gmail.com>

On 09/02/2013 05:01 PM, Laurent Pinchart wrote:
> Hi Lars-Peter,
> 
> On Monday 02 September 2013 16:43:25 Lars-Peter Clausen wrote:
>> On 09/02/2013 04:15 PM, Laurent Pinchart wrote:
>>> On Monday 02 September 2013 15:40:22 Lars-Peter Clausen wrote:
>>>> On 09/02/2013 03:18 PM, Laurent Pinchart wrote:
>>>>> On Friday 30 August 2013 14:37:35 Ulrich Hecht wrote:
>>>>>> ADV7511 driver snapshot taken from commit f416e32 of xcomm_zynq_3_10
>>>>>> branch at https://github.com/analogdevicesinc/linux.git
>>>>>
>>>>> I believe Lars-Peter (CC'ed) was planning to upstream the driver.
>>>>> Lars-Peter, could you please share your plans ?
>>>>
>>>> My plan was to have all this upstream long time ago ;)
>>>>
>>>> As I said in that other thread, I don't think it is a good idea to have
>>>> two drivers for the same device. But if nobody else sees a problem with
>>>> this and as long as the v4l driver doesn't have devicetree support I
>>>> guess we could get away with it for now. Even if it will probably haunt
>>>> us later on.
>>>>
>>>> There are still a few minor bits and pieces to iron out, but lets try to
>>>> aim for 2.6.13.
>>>
>>> If you can make it for 2.6.13 I will be extremely impressed :-)
>>
>> Yea, I know DRM always takes a bit longer...
> 
> I think you meant 3.13 ;-)
> 
>>> Do you plan to push the driver yourself ? If so, I would appreciate if you
>>> could CC me. If there's just a few minor bits to iron out I can already
>>> review your latest version if that can help.
>>
>> There are a couple of style issues, so if you review the driver ignore these
>> for now, but otherwise feedback is welcome, thanks. And I'm not also quite
>> happy with the ASoC integration yet.
> 
> Sure. Is the version available from the above branch the latest version ?

Yes, you can find it here:
https://github.com/analogdevicesinc/linux/tree/xcomm_zynq/drivers/gpu/drm/i2c

Oh and the DT bindings also still need proper documentation.

- Lars

  parent reply	other threads:[~2013-09-02 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 12:37 [RFC 01/10] drm: ADV7511 i2c HDMI encoder driver Ulrich Hecht
2013-09-02 13:18 ` Laurent Pinchart
2013-09-02 13:40 ` Lars-Peter Clausen
2013-09-02 14:15 ` Laurent Pinchart
2013-09-02 14:43 ` Lars-Peter Clausen
2013-09-02 15:01 ` Laurent Pinchart
2013-09-02 15:09 ` Lars-Peter Clausen [this message]
2013-09-03 16:13   ` Laurent Pinchart
2013-09-04 11:34     ` Lars-Peter Clausen
2013-09-11  9:33       ` Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2013-08-30 12:37 [RFC 00/10] Lager HDMI support Ulrich Hecht

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=5224AA17.6060806@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-sh@vger.kernel.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).