public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Sebastian Reichel <sre@debian.org>,
	Benoit Cousson <bcousson@baylibre.com>,
	Pavel Machek <pavel@ucw.cz>,
	Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: dts: n900: isp1704 gpio
Date: Thu, 27 Nov 2014 09:22:16 -0600	[thread overview]
Message-ID: <20141127152216.GD30719@saruman> (raw)
In-Reply-To: <201411271513.43349@pali>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Hi,

On Thu, Nov 27, 2014 at 03:13:43PM +0100, Pali Rohár wrote:
> Hello,
> 
> in commit "ARM: dts: OMAP3-N900: Add isp1704 support" 
> e17337a26962943c27124a14b0794eabe76af437 was added support for 
> isp1704 chip with configured gpio "3". Now I looked into legacy 
> board rx51 data and there is gpio "67" for isp1704.
> 
> I would like to ask, why we have different gpio in board data and 
> in DTS data? I'm sure that isp1704 worked from legacy board data 
> without problem, so I do not understand why in DTS code is 
> different gpio number.

it's magic! Seriously though, each GPIO bank as 32 GPIOs with numbers
starting at 0, note that DTS uses the 3rd GPIO line on the 3rd GPIO
bank.

Bank0 handles GPIOs 0 - 31, Bank1 handles GPIOs 32 - 63, Bank 2 handles
GPIOs 64 - 95, and so on...

Offset 3 on Bank 3 would be 64 + 3 == 67. Yay, magic.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2014-11-27 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 14:13 dts: n900: isp1704 gpio Pali Rohár
2014-11-27 15:22 ` Felipe Balbi [this message]

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=20141127152216.GD30719@saruman \
    --to=balbi@ti.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=bcousson@baylibre.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=sre@debian.org \
    --cc=tony@atomide.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