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: [RFC PATCH arm: initial TI-Nspire support]
Date: Tue, 09 Apr 2013 13:01:56 +0100	[thread overview]
Message-ID: <1365508916.24306.17.camel@hornet> (raw)
In-Reply-To: <CACRpkda9Nue-8Esp3cJ6u2-MJ2ZL8hH-2BnrhHwWv4GZP2VR5w@mail.gmail.com>

On Tue, 2013-04-09 at 12:23 +0100, Linus Walleij wrote:
> On Sun, Apr 7, 2013 at 11:23 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Sunday 07 April 2013, Daniel Tang wrote:
> >> Here's an updated patch that enables support for the LCD.
> >>
> >> I looked into drivers/video/of_display_timing.c but it doesn't have the fields to describe the
> >> PL11x specific options needed in struct clcd_panel. At the moment, it is implemented by
> >> hardcoding the values in the kernel and using the device tree to select the correct
> >> configuration.
> >>
> >> Signed-off-by: Daniel Tang <dt.tangr@gmail.com>
> >
> > I think you should for now keep the clcd stuff in a separate file,
> > since it will be replaced with DT logic eventually. For now, the
> > auxdata method is ok, but Linus Walleij might already have thought
> > about how pl111 should get all its data from the device tree.
> 
> So last thing I heard there was *someone* at ARM working on
> device tree support for the PL110/PL111, so I just don't know who
> this was.
> 
> But I bet Pawel knows, because it will be needed for all
> ARM reference designs.

So I have PL111 code almost working here, however today it depends on
not-yet-upstream (to my knowledge) generic/common panel/display
framework. If I'm not disturbed again I may get something done this
week, hopefully removing the dependency.

There's also some work going on on a DRM driver for PL111, but I can't
promise any dates.

As to PL110 I have no idea how different is it from the PL111, but
nothing is happening about it anyway.

Pawe?

  reply	other threads:[~2013-04-09 12:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  9:01 [RFC PATCH arm: initial TI-Nspire support] Daniel Tang
2013-04-04 11:12 ` Arnd Bergmann
2013-04-06  0:26   ` Daniel Tang
2013-04-06 11:51     ` Arnd Bergmann
2013-04-06 12:00       ` Daniel Tang
2013-04-06 13:24         ` Arnd Bergmann
2013-04-07  0:06           ` Daniel Tang
2013-04-07  3:56             ` Daniel Tang
2013-04-07 21:23               ` Arnd Bergmann
2013-04-08 11:33                 ` Daniel Tang
2013-04-08 19:16                   ` Fabian Vogt
2013-04-08 19:38                     ` Arnd Bergmann
2013-04-08 20:06                       ` Fabian Vogt
2013-04-08 21:29                         ` Arnd Bergmann
2013-04-09  5:59                     ` Daniel Tang
2013-04-09 11:23                 ` Linus Walleij
2013-04-09 12:01                   ` Pawel Moll [this message]
2013-04-09 12:05                     ` Linus Walleij
2013-04-09 13:51                     ` Russell King - ARM Linux
2013-04-07 14:32             ` Arnd Bergmann
2013-04-09 11:14 ` Linus Walleij
2013-04-09 11:39   ` Daniel Tang
2013-04-09 11:58     ` Linus Walleij

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=1365508916.24306.17.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