From: Stephen Warren <swarren@wwwdotorg.org>
To: Ashwini Ghuge <aghuge@nvidia.com>,
rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
rob@landley.net, linus.walleij@linaro.org,
grant.likely@linaro.org, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] pinctrl: tegra124: add pinctrl driver for NVIDIA's Tegra124 SoC
Date: Wed, 04 Dec 2013 12:30:48 -0700 [thread overview]
Message-ID: <529F82E8.3000206@wwwdotorg.org> (raw)
In-Reply-To: <1384191718-16817-1-git-send-email-aghuge@nvidia.com>
On 11/11/2013 10:41 AM, Ashwini Ghuge wrote:
> The driver uses the common Tegra pinctrl driver utility functions to
> implement the majority of the driver. It is based on the similar Tegra114
> pinctrl
> +static const struct tegra_function tegra124_functions[] = {
...
> + FUNCTION(i2c1),
> + FUNCTION(i2c2),
> + FUNCTION(i2c3),
> + FUNCTION(i2c4),
> + FUNCTION(i2cpwr),
Is that complete? Tegra124 apparently has 6 I2C controllers. Are the
pins for the new sixth controller (0x7000d100) not affected by the pinmux?
prev parent reply other threads:[~2013-12-04 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:41 [PATCH] pinctrl: tegra124: add pinctrl driver for NVIDIA's Tegra124 SoC Ashwini Ghuge
2013-11-11 18:01 ` Mark Rutland
[not found] ` <20131111180124.GA27735-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-11-11 18:24 ` Stephen Warren
[not found] ` <528120EF.1030000-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-12 9:19 ` Mark Rutland
2013-12-04 19:30 ` Stephen Warren [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=529F82E8.3000206@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=aghuge@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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).