From: Timur Tabi <timur@codeaurora.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: MSM8974: Add pinctrl node
Date: Mon, 7 Apr 2014 18:53:02 -0500 [thread overview]
Message-ID: <CAOZdJXVE7MSMBaL+bt0kjw5LEidz-aVp+vrWqQWkye6HdE7EeA@mail.gmail.com> (raw)
In-Reply-To: <1391700529-11816-2-git-send-email-iivanov@mm-sol.com>
On Thu, Feb 6, 2014 at 9:28 AM, Ivan T. Ivanov <iivanov@mm-sol.com> wrote:
> + spi8_default: spi8_default {
> + mosi {
> + pins = "gpio45";
> + function = "blsp_spi8";
> + };
> + miso {
> + pins = "gpio46";
> + function = "blsp_spi8";
> + };
> + cs {
> + pins = "gpio47";
> + function = "blsp_spi8";
> + };
> + clk {
> + pins = "gpio48";
> + function = "blsp_spi8";
> + };
I'm confused by this. Isn't this information already defined in the
pinctrl-msm8x74.c driver?
static const char * const blsp_spi8_groups[] = {
"gpio45", "gpio46", "gpio47", "gpio48"
};
next prev parent reply other threads:[~2014-04-07 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391700529-11816-1-git-send-email-iivanov@mm-sol.com>
2014-02-06 15:28 ` [PATCH 2/2] ARM: dts: MSM8974: Add pinctrl node Ivan T. Ivanov
2014-02-10 18:55 ` Bjorn Andersson
2014-02-11 20:28 ` Kumar Gala
[not found] ` <1391700529-11816-2-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2014-02-24 9:57 ` Linus Walleij
2014-02-25 15:50 ` Kumar Gala
2014-04-07 23:53 ` Timur Tabi [this message]
2014-04-08 12:14 ` Ivan T. Ivanov
2014-04-08 12:33 ` Timur Tabi
2014-04-08 13:46 ` Ivan T. Ivanov
2014-04-08 14:18 ` Timur Tabi
2014-04-08 15:26 ` Timur Tabi
2014-04-08 18:39 ` Bjorn Andersson
2014-04-10 16:22 ` Linus Walleij
2014-04-08 12:12 ` Timur Tabi
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=CAOZdJXVE7MSMBaL+bt0kjw5LEidz-aVp+vrWqQWkye6HdE7EeA@mail.gmail.com \
--to=timur@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).