From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: LVDS (LDB) driver for i.MX53 IPU
Date: Sun, 10 Mar 2013 23:32:41 +0100 [thread overview]
Message-ID: <20130310223241.GQ1906@pengutronix.de> (raw)
In-Reply-To: <5134DF0E.7010402@parkeon.com>
Hi Martin,
On Mon, Mar 04, 2013 at 06:51:10PM +0100, Martin Fuzzey wrote:
> Hi Sascha,
>
> I need to add LVDS support to your staging imx/drm driver.
>
> First of all are there any patches floating around to do that? (a
> search of the mailing list didn't turn up any).
>
> From a hardware point of view it looks quite simple (just one
> register to configure) but unfortunately that register is in the
> IOMUXC region.
>
> That means that if I write a new platform driver similar to
> drivers/staging/imx-drm/parallel-display.c (with a new DT node
> pointing to the reg) the request_resource() will fail since it will
> already be claimed by the iomuxc driver.
>
> The only solutions I can think of are:
> 1) Add exported function to the iomuxc driver to get the register
> or
> 2) Directly ioremap() the address
>
> Both of these sound horrible.
>
> Do you have any suggestions?
>
> I guess the generic question I'm asking is how to handle the case
> where unrelated drivers require access to the same memory regions?
>
We have a driver for the ldb. Indeed the driver itself is trivial, but
the integration is tricky. For accessing the register the syscon binding
can be used. The clock is also a problem, also the mux to the IPU(s)
I'll talk with Philipp tomorrow and I think we can send you the current
state then.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-03-10 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 17:51 LVDS (LDB) driver for i.MX53 IPU Martin Fuzzey
2013-03-10 22:32 ` Sascha Hauer [this message]
2013-05-24 12:35 ` Guennadi Liakhovetski
2013-05-24 13:12 ` Martin Fuzzey
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=20130310223241.GQ1906@pengutronix.de \
--to=s.hauer@pengutronix.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).