From: Sylwester Nawrocki <snjw23@gmail.com>
To: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Handling device shared SFR on dt platform
Date: Wed, 21 Mar 2012 23:38:11 +0100 [thread overview]
Message-ID: <4F6A5853.9090809@gmail.com> (raw)
Hello,
I'm working on adding the device tree support for two devices that
share some IO registers. Exactly, there is one shared SFR that
contains a common bit to enable two PHY devices, and another two
bits, each to separately reset each PHY.
Currently this shared register is statically memory mapped and it is
handled by a platform specific callback, that both drivers use to
control their corresponding (sub)devices in synchronised manner.
The two devices are a MIPI-CSI2 receiver and a MIPI-DSI transmitter,
and the common register is there to control the camera and the display
port PHY. The hardware design is a bit unfortunate, but there is not
much I could do about it.
The callback can be looked at at:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=arch/arm/plat-s5p/setup-mipiphy.c
I have been trying to find method to handle this on a dt platform.
Has anyone faced similar issue before ? I would appreciate any ideas
or suggestions.
One of ideas was to create some sort of PHY framework, similar to
clock API, and perhaps handle such platform quirks outside DT.
--
Thanks,
Sylwester
next reply other threads:[~2012-03-21 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 22:38 Sylwester Nawrocki [this message]
2012-03-24 19:32 ` Handling device shared SFR on dt platform Grant Likely
2012-03-28 19:45 ` Sylwester Nawrocki
2012-04-03 16:04 ` Grant Likely
2012-04-04 20:35 ` Sylwester Nawrocki
[not found] ` <4F7CB0A6.7010809-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-07 1:41 ` Grant Likely
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=4F6A5853.9090809@gmail.com \
--to=snjw23@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--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).