All of lore.kernel.org
 help / color / mirror / Atom feed
From: stefan.wahren@i2se.com (Stefan Wahren)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Overlapping regions in DT
Date: Wed, 11 Feb 2015 16:49:55 +0100	[thread overview]
Message-ID: <54DB7A23.4000502@i2se.com> (raw)
In-Reply-To: <CABM=7kkcbj1Yxot=FEB3Z0OtWbJ=oDue76uSnAmZndhG=eJp=A@mail.gmail.com>

Hi Tsahee,

Am 09.02.2015 um 09:22 schrieb Tsahee Zidenberg:
> syscon regmap is one possible way to access a register file from two
> different drivers without mapping it twice. But in that case you loose
> the name-per-register in devicetree. The devtree maps the general
> regfile, and the drivers know the offsets by themselves.
> Have a look here:
> Have a look: http://thread.gmane.org/gmane.linux.kernel/1352299

thanks for your suggestion. I'll give it a try.

Stefan

WARNING: multiple messages have this Message-ID (diff)
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: Overlapping regions in DT
Date: Wed, 11 Feb 2015 16:49:55 +0100	[thread overview]
Message-ID: <54DB7A23.4000502@i2se.com> (raw)
In-Reply-To: <CABM=7kkcbj1Yxot=FEB3Z0OtWbJ=oDue76uSnAmZndhG=eJp=A@mail.gmail.com>

Hi Tsahee,

Am 09.02.2015 um 09:22 schrieb Tsahee Zidenberg:
> syscon regmap is one possible way to access a register file from two
> different drivers without mapping it twice. But in that case you loose
> the name-per-register in devicetree. The devtree maps the general
> regfile, and the drivers know the offsets by themselves.
> Have a look here:
> Have a look: http://thread.gmane.org/gmane.linux.kernel/1352299

thanks for your suggestion. I'll give it a try.

Stefan

  reply	other threads:[~2015-02-11 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08  3:17 Overlapping regions in DT Stefan Wahren
2015-02-08  3:17 ` Stefan Wahren
2015-02-09  8:22 ` Tsahee Zidenberg
2015-02-11 15:49   ` Stefan Wahren [this message]
2015-02-11 15:49     ` Stefan Wahren

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=54DB7A23.4000502@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.