From: Imre Deak <imre.deak@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Valkeinen Tomi (Nokia-D/Helsinki)" <Tomi.Valkeinen@nokia.com>
Subject: Re: LDP support
Date: Thu, 4 Jun 2009 00:39:55 +0300 [thread overview]
Message-ID: <20090603213955.GA24318@localhost> (raw)
In-Reply-To: <20090601160032.GA4825@atomide.com>
On Mon, Jun 01, 2009 at 06:00:33PM +0200, ext Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [090531 14:25]:
> > On Tue, Apr 28, 2009 at 03:42:37PM -0700, Tony Lindgren wrote:
> > > * Russell King - ARM Linux <linux@arm.linux.org.uk> [090428 15:07]:
> > > > Tony, et.al.,
> > > >
> > > > Any ideas when more LDP support will be pushed into mainline (such as
> > > > the framebuffer support)?
> > >
> > > I'll be looking at the board-*.c patches for the next merge window
> > > hopefully this week or next week.
> > >
> > > Looks like LDP keyboard, touchscreen & RTC are pretty much ready
> > > to go. Then the MMC has some regulator updates, but AFAIK the MMC
> > > should work OK already.
> > >
> > > For the framebuffer, Imre and Tomi know the status the best, so
> > > I've added them to Cc.
> > >
> > > Imre has been meaning to send a bunch of drivers/video/omap changes
> > > to the fbdev list for a while now and LDP framebuffer may depend on
> > > those. Imre, any news on the status of sending the fb patches
> > > upstream?
> > >
> > > Then there are the upcoming DSS patches from Tomi, but those still
> > > need some work before they're ready to go.
> >
> > Okay, now that I've merged your tree, we've moved a few steps forward but
> > a couple of steps backward with LDP support:
> >
> > 1. LDP LCD platform device added
> > 2. GPIO keyboard platform data added
> > 3. TWL4030 keyboard platform data added
> > 4. TSC2046 touchscreen platform data added
> > 5. MMC has regressed - no sign of the driver initializing, not even an
> > error message from it, so I can't boot to check what the status of
> > these are.
>
> Do you have CONFIG_REGULATOR set in your .config? That seems to be missing
> from arch/arm/configs/omap_ldp_defconfig.
>
> > 6. do ___NOT___ (underscored in triplicate and 500ft high letters) enable
> > ARM errata 460075 - it solidly prevents the kernel booting on LDP.
> > (it's taken many hours to debug that.)
> >
> > However, things that still seem to be missing:
> >
> > 1. GPIO keyboard (presumably) needs to be enabled in omap_ldp_defconfig
>
> Anybody with an LDP care to update the omap_ldp_defconfig? No LDP here.
>
> > 2. No TWL4030 keyboard driver merged (not even in linux-next)
> > 3. No LDP LCD driver merged
> > 4. No OMAP3 video driver
>
> For 3 & 4, I know Imre has the patches ready to go.. Imre, have they been
> posted to the fb list?
Not yet, I updated the patches, removing the board file changes as we agreed.
Also they don't include the latest HWA742 clock changes, which should be already
in the omap-fixes queue.
Other than these the patches have the following changes based on the omap-fixes
version of the driver:
- checkpatch fixes
- logically related commits merged, keeping the authorship info
- commit removed: omapfb: remove wrong scale call for gfx_plane
This can't be correct, as it disables scaling completely.
I updated the omapfb-upstream branch on git://koowaldah.org/people/imre/linux-2.6-fb,
if these are ok with you I'll post them on the fb list.
--Imre
next prev parent reply other threads:[~2009-06-03 21:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 22:07 LDP support Russell King - ARM Linux
2009-04-28 22:42 ` Tony Lindgren
2009-04-30 17:28 ` Koen Kooi
2009-05-05 19:52 ` Russell King - ARM Linux
2009-05-06 4:00 ` Tony Lindgren
2009-05-06 22:49 ` [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support) Tony Lindgren
2009-05-07 15:01 ` stanley.miao
2009-05-07 16:19 ` Russell King - ARM Linux
2009-05-07 16:28 ` Tony Lindgren
2009-05-07 16:34 ` Russell King - ARM Linux
2009-05-07 16:37 ` Russell King - ARM Linux
2009-05-07 16:41 ` Tony Lindgren
2009-05-07 16:56 ` Koen Kooi
2009-05-07 17:18 ` Tony Lindgren
2009-05-07 18:45 ` Koen Kooi
2009-05-08 3:26 ` stanley.miao
2009-05-08 3:27 ` Gadiyar, Anand
2009-05-08 9:18 ` stanley.miao
2009-05-08 15:22 ` Tony Lindgren
2009-05-08 16:47 ` Kalle Valo
2009-05-16 8:19 ` Russell King - ARM Linux
2009-05-18 15:54 ` Kalle Valo
2009-05-18 16:09 ` Russell King - ARM Linux
2009-05-18 17:13 ` Kevin Hilman
2009-05-18 18:59 ` Russell King - ARM Linux
2009-05-19 20:54 ` Jon Hunter
2009-05-07 21:42 ` Tony Lindgren
2009-05-14 9:07 ` LDP support Imre Deak
2009-05-14 17:33 ` Tony Lindgren
2009-05-31 21:24 ` Russell King - ARM Linux
2009-06-01 0:24 ` Woodruff, Richard
2009-06-01 7:45 ` Russell King - ARM Linux
2009-06-01 15:18 ` Woodruff, Richard
2009-06-01 15:26 ` Woodruff, Richard
2009-06-01 4:51 ` Felipe Balbi
2009-06-01 16:00 ` Tony Lindgren
2009-06-01 16:16 ` Russell King - ARM Linux
2009-06-03 21:39 ` Imre Deak [this message]
2009-06-03 22:33 ` Russell King - ARM Linux
2009-06-03 23:41 ` Tony Lindgren
2009-06-04 14:58 ` Imre Deak
2009-06-04 15:25 ` Tony Lindgren
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=20090603213955.GA24318@localhost \
--to=imre.deak@nokia.com \
--cc=Tomi.Valkeinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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