public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: Sharing resources between several drivers.
Date: Sat, 28 Jul 2012 22:07:54 +0800	[thread overview]
Message-ID: <20120728140751.GI2128@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433EB1F69E@DBDE01.ent.ti.com>

On Fri, Jul 27, 2012 at 09:03:33AM +0000, Bedia, Vaibhav wrote:
> On Fri, Jul 27, 2012 at 13:29:21, javier Martin wrote:
> > Hi,
> > we are trying to support pinctrl for i.MX21, i.MX1 and i.MX27.
> > 
> > In these chips, gpio and pinctrl use the same HW memory area
> > registers. This means that we have to request the same memory area
> > from two different drivers (gpio and pinctrl) but we don't know how to
> > do that.
> > 
> > A similar example available is mxs, but it only works with device
> > tree, so this problem is avoided.  However, some of these chips
> 
> I am curious as to how device tree solves the access issues for
> a shared resource.
> 
Although pinctrl and gpio share the same IO region, they are accessing
different registers, so there should be no access issues.

-- 
Regards,
Shawn

  reply	other threads:[~2012-07-28 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  7:59 Sharing resources between several drivers javier Martin
2012-07-27  9:03 ` Bedia, Vaibhav
2012-07-28 14:07   ` Shawn Guo [this message]
2012-07-30 12:00     ` Bedia, Vaibhav
2012-07-27  9:19 ` Thomas Petazzoni
2012-07-27  9:33   ` javier Martin
2012-07-29 14:19 ` Arnd Bergmann
2012-08-04 23:46   ` Linus Walleij

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=20120728140751.GI2128@S2101-09.ap.freescale.net \
    --to=shawn.guo@linaro.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