From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: vexpress: hook platform_data to clcd_pl11x by amba bus_notify
Date: Mon, 17 Dec 2012 12:55:23 +0000 [thread overview]
Message-ID: <20121217125523.GS14363@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1355747549.2978.5.camel@hornet>
On Mon, Dec 17, 2012 at 12:32:29PM +0000, Pawel Moll wrote:
> On Sat, 2012-12-15 at 05:39 +0000, Barry Song wrote:
> > From: Barry Song <Baohua.Song@csr.com>
> >
> > when using dtb to boot v2p-ca9, clcd probe will fail due to missed
> > the platform_data:
> > clcd-pl11x: probe of 10020000.clcd failed with error -22
> > this patch hooks the platform_data to clcd and make lcd of v2p-ca9
> > can work while booting vexpress by DTB.
> > Tested on qemu by "qemu-system-arm -M vexpress-a9 -m 512M -kernel
> > zImage -dtb ./vexpress-v2p-ca9.dtb"
> >
> > Signed-off-by: Barry Song <Baohua.Song@csr.com>
>
> Thanks for your work, however there are some problems with your code,
> especially if you look at the changes being merged right now for 3.8
> kernel... The clocking implementation is completely changed (actually
> you should not need any extra CLCD information now), and as the auxdata
> for devices population is removed, you could use it instead of the -
> slightly strange to my taste - notifier-based solution.
>
> Now having said all that, I'm hoping to get comprehensive solution for
> DT-based VE display devices ready in time for 3.9, which will sort out
> the issue once for all.
It has? Why haven't I been copied on the CLCD driver patches then?
next prev parent reply other threads:[~2012-12-17 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 5:39 [PATCH] arm: vexpress: hook platform_data to clcd_pl11x by amba bus_notify Barry Song
2012-12-17 12:32 ` Pawel Moll
2012-12-17 12:39 ` Barry Song
2012-12-17 12:43 ` Pawel Moll
2012-12-17 12:55 ` Russell King - ARM Linux [this message]
2012-12-17 13:52 ` Pawel Moll
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=20121217125523.GS14363@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).