From: sre@ring0.de (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: N900 board code in 3.14
Date: Sat, 16 Nov 2013 15:50:33 +0000 [thread overview]
Message-ID: <20131116155031.GA5104@earth.universe> (raw)
In-Reply-To: <20131116141226.GD10317@atomide.com>
On Sat, Nov 16, 2013 at 06:12:26AM -0800, Tony Lindgren wrote:
> [...]
> > b) I could not get the 32GB eMMC working. For me the chip is not found
> > and I don't know how to debug it.
>
> OK the eMMC issue might be related to the control module PBIAS
> register support missing. If so, that should be fixable with the
> auxdata until we have a minimal control module device driver to
> deal with the PBIAS and expose those features as regulators to
> the omap-hsmmc driver.
I wasn't aware, that PBIAS register support is missing for DT
boot. The existing board code uses a 2.8-3.0V regulator for mmc1,
so missing PBIAS is probably the problem.
> > [...]
> >
> > My suggestion would be:
> > 1. Find a better workaround for omapdss to acquire the SDI
> > regulator. My current hack is obviously not acceptable.
> > 2. Load the panel driver via DT as seen above and reference
> > the omapdss interface with something like the above
> > "ti,dss-source".
>
> To me it seems that we should be able to add minimal panel entries to DT
> if we stick to existing standard bindings. Then the timings etc can be
> set up based on the compatible flag. So I would leave out the properties
> for ti,sdi-datapairs and ti,dss-source for now, and just set those in
> the driver based on the sony,acx565akm compatible flag. Or maybe it should
> be sony,acx565akm-n900 if there's some board specific configuration info.
So we add reset-gpio and label to the DT data (they are panel
specific and independent of omapdss) and just hardcode "dsi.0"
with 2 data lanes into the driver? That sounds fine for me.
If neither Tomi nor anybody else has better ideas I will cook a
patch for that. I'm not sure how to setup the vdds_sdi regulator for
omapdss, though. Is there an example for a legacy driver using a DT
regulator available?
> [...]
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131116/a814c255/attachment.sig>
next prev parent reply other threads:[~2013-11-16 15:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 0:36 [PATCH 0/5] Prepare making omap3 device tree only and convert LDP Tony Lindgren
2013-11-16 0:36 ` [PATCH 1/5] mfd: twl-core: Fix passing of platform data in the device tree case Tony Lindgren
2013-11-18 10:29 ` Lee Jones
2013-11-18 17:25 ` Felipe Balbi
2013-11-18 17:46 ` Lee Jones
2013-11-18 18:11 ` Tony Lindgren
2013-11-18 19:09 ` Lee Jones
2013-11-18 19:22 ` Tony Lindgren
2013-11-18 19:28 ` Lee Jones
2013-11-18 19:33 ` Tony Lindgren
2013-11-21 10:46 ` Lee Jones
2013-11-21 11:09 ` Lee Jones
2013-11-25 23:22 ` Tony Lindgren
2013-11-18 18:40 ` Felipe Balbi
2013-11-16 0:36 ` [PATCH 2/5] ARM: OMAP2+: Add support for legacy auxdata for twl Tony Lindgren
2013-11-16 0:36 ` [PATCH 3/5] ARM: OMAP2+: Add DT init code for DPI displays and make omap3 LDP to use it Tony Lindgren
2013-11-18 13:06 ` Tomi Valkeinen
2013-11-18 18:19 ` Tony Lindgren
2013-11-16 0:36 ` [PATCH 4/5] ARM: dts: Add basic support for omap3 LDP zoom1 labrador Tony Lindgren
2013-11-16 8:04 ` Sebastian Reichel
2013-11-16 14:40 ` Tony Lindgren
2013-11-16 0:36 ` [PATCH 5/5] ARM: OMAP2+: Remove legacy booting support for LDP Tony Lindgren
[not found] ` <20131116120508.GA22335@earth.universe>
2013-11-16 14:12 ` N900 board code in 3.14 Tony Lindgren
2013-11-16 15:50 ` Sebastian Reichel [this message]
2013-11-21 18:58 ` Tony Lindgren
2013-11-21 23:51 ` Sebastian Reichel
2013-11-22 10:41 ` Javier Martinez Canillas
2013-11-23 21:09 ` Sebastian Reichel
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=20131116155031.GA5104@earth.universe \
--to=sre@ring0.de \
--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).