From: mfuzzey@parkeon•com (Martin Fuzzey)
To: linux-arm-kernel@lists•infradead.org
Subject: LVDS (LDB) driver for i.MX53 IPU
Date: Mon, 04 Mar 2013 18:51:10 +0100 [thread overview]
Message-ID: <5134DF0E.7010402@parkeon.com> (raw)
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?
Regards,
Martin
next reply other threads:[~2013-03-04 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 17:51 Martin Fuzzey [this message]
2013-03-10 22:32 ` LVDS (LDB) driver for i.MX53 IPU Sascha Hauer
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=5134DF0E.7010402@parkeon.com \
--to=mfuzzey@parkeon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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