public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ARM: integrator: multiplatform advancements
Date: Wed, 05 Mar 2014 16:19:54 +0000	[thread overview]
Message-ID: <1394036394.4160.12.camel@hornet> (raw)
In-Reply-To: <CACRpkdYfbgi_PY_OJpifzaS9x1fgLhGir05VS7BAw4QT5ZGMmQ@mail.gmail.com>

On Mon, 2014-02-24 at 09:37 +0000, Linus Walleij wrote:
> On Fri, Feb 14, 2014 at 2:47 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Fri, Feb 14, 2014 at 11:29:25AM +0100, Linus Walleij wrote:
> >> The *real* solution, one might argue is to convert the CLCD
> >> driver to DRM and add device tree bindings, but it appears that
> >> this is an orthogonal goal that has been attempted by other with
> >> mixed results.
> >
> > What mixed results?  You know, I find it rather sick that people run
> > around trying to do this to a driver that I authored and maintain
> > without one comment to me about it.  It sometimes feels like people
> > think I don't exist anymore.
> 
> Sorry, I was referring to this driver for PL111:
> http://marc.info/?l=linux-arm-kernel&m=137477285809710&w=2
> 
> So I take it that the PL111 is a totally different beast from
> PL110 except for the single digit difference in the name.
> Whereas PL180 and PL181 are essentially the same piece
> of hardware...
> 
> Then there is this patch set for DT support for the CLCD which
> appears to be orthogonal:
> http://marc.info/?l=linux-arm-kernel&m=137968689722364&w=2
> 
> Pawel, is this coming along?

Last week I was about to answer that this was my last word in the
subject ;-) but then I decided to give it another go, trying to address
the last - I think - controversial bit, being the pads property. Made it
much simpler and optional, so it should be in anybody's (namely the DRM
driver and bindings) way.

Will post in a second.

Pawel

      reply	other threads:[~2014-03-05 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 10:29 [PATCH 0/6] ARM: integrator: multiplatform advancements Linus Walleij
2014-02-14 10:29 ` [PATCH 1/6] ARM: integrator: localize the lm.h header Linus Walleij
2014-02-14 10:29 ` [PATCH 2/6] ARM: integrator: localize the impd1.h header Linus Walleij
2014-02-14 10:29 ` [PATCH 3/6] ARM: integrator: merge platform.h to hardware.h Linus Walleij
2014-02-14 10:29 ` [PATCH 4/6] ARM: integrator: localize the hardware.h header Linus Walleij
2014-02-14 10:29 ` [PATCH 5/6] ARM: integrator: register sched_clock directly Linus Walleij
2014-02-14 10:29 ` [PATCH 6/6] RFC: ARM: integrator: get rid of <mach/memory.h> Linus Walleij
2014-02-14 12:02   ` Arnd Bergmann
2014-02-14 13:47 ` [PATCH 0/6] ARM: integrator: multiplatform advancements Russell King - ARM Linux
2014-02-24  9:37   ` Linus Walleij
2014-03-05 16:19     ` Pawel Moll [this message]

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=1394036394.4160.12.camel@hornet \
    --to=pawel.moll@arm.com \
    --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