From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra30: tegra30 gpio is not compatible with tegra20 gpio
Date: Thu, 20 Dec 2012 11:46:57 +0530 [thread overview]
Message-ID: <50D2AD59.8070901@nvidia.com> (raw)
In-Reply-To: <50D1F385.7000506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Wednesday 19 December 2012 10:34 PM, Stephen Warren wrote:
> On 12/19/2012 07:57 AM, Laxman Dewangan wrote:
>> tegra30 gpio controller is not compatible with the tegra20 due to
>> their bank stride i.e. Tegra20 bank stride is 0x80 where Tegra30
>> bank stride is 0x100.
> Thanks, I've been meaning to clean this up for a while, but never got
> around to it. I can apply after the merge window is closed; I don't
> think it's important enough to warrant going into 3.8 or earlier, since
> it doesn't cause any active problems.
>
> Have you checked all the other devices to make sure they're all correct to?
Not yet, I am going one by one for finding if anything we are missing
on IO drivers or not and then came across this.
next prev parent reply other threads:[~2012-12-20 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 14:57 [PATCH] ARM: tegra30: tegra30 gpio is not compatible with tegra20 gpio Laxman Dewangan
[not found] ` <1355929032-26549-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 17:04 ` Stephen Warren
[not found] ` <50D1F385.7000506-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-20 6:16 ` Laxman Dewangan [this message]
2013-01-02 19:07 ` Stephen Warren
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=50D2AD59.8070901@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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).