From: Grant Likely <grant.likely@secretlab.ca>
To: Sylwester Nawrocki <snjw23@gmail.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Handling device shared SFR on dt platform
Date: Sat, 24 Mar 2012 19:32:00 +0000 [thread overview]
Message-ID: <20120324193200.822AD3E0B06@localhost> (raw)
In-Reply-To: <4F6A5853.9090809@gmail.com>
On Wed, 21 Mar 2012 23:38:11 +0100, Sylwester Nawrocki <snjw23@gmail.com> wrote:
>
> 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.
Generally, this is handled by having a third node for the shared
register block and both device nodes holding a phandle to it.
No, there isn't any common infrastructure for implementing this, but
it isn't very much code.
g.
next prev parent reply other threads:[~2012-03-24 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 22:38 Handling device shared SFR on dt platform Sylwester Nawrocki
2012-03-24 19:32 ` Grant Likely [this message]
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=20120324193200.822AD3E0B06@localhost \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=snjw23@gmail.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;
as well as URLs for NNTP newsgroup(s).