From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: <devicetree@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Gregory Clement <gregory.clement@bootlin.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nadav Haklai <nadavh@marvell.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
<linux-arm-kernel@lists.infradead.org>,
Grzegorz Jaszczyk <jaz@semihalf.com>,
Marcin Wojtas <mw@semihalf.com>,
Stefan Chulski <stefanc@marvell.com>,
Yan Markman <ymarkman@marvell.com>,
Konstantin Porotchkin <kostap@marvell.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH 1/3] pinctrl: mvebu: Add CP110 missing pin functionality
Date: Mon, 5 Aug 2019 12:16:05 +0200 [thread overview]
Message-ID: <20190805101607.29811-2-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20190805101607.29811-1-miquel.raynal@bootlin.com>
From: Konstantin Porotchkin <kostap@marvell.com>
Add missing definition for function 0xe on CP-110 MPP-62.
The pin function is Data Strobe for SDIO interface.
Signed-off-by: Konstantin Porotchkin <kostap@marvell.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
drivers/pinctrl/mvebu/pinctrl-armada-cp110.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/mvebu/pinctrl-armada-cp110.c b/drivers/pinctrl/mvebu/pinctrl-armada-cp110.c
index 584952b2ba47..85ade9761885 100644
--- a/drivers/pinctrl/mvebu/pinctrl-armada-cp110.c
+++ b/drivers/pinctrl/mvebu/pinctrl-armada-cp110.c
@@ -597,7 +597,8 @@ static struct mvebu_mpp_mode armada_cp110_mpp_modes[] = {
MPP_FUNCTION(7, "uart0", "rxd"),
MPP_FUNCTION(8, "uart2", "rxd"),
MPP_FUNCTION(9, "sata0", "present_act"),
- MPP_FUNCTION(10, "ge", "mdc")),
+ MPP_FUNCTION(10, "ge", "mdc"),
+ MPP_FUNCTION(14, "sdio", "ds")),
};
static const struct of_device_id armada_cp110_pinctrl_of_match[] = {
--
2.20.1
next prev parent reply other threads:[~2019-08-05 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 10:16 [PATCH 0/3] CP115 pinctrl support Miquel Raynal
2019-08-05 10:16 ` Miquel Raynal [this message]
2019-08-27 7:48 ` [PATCH 1/3] pinctrl: mvebu: Add CP110 missing pin functionality Linus Walleij
2019-08-05 10:16 ` [PATCH 2/3] dt-bindings: cp110: document the new CP115 pinctrl compatible Miquel Raynal
2019-08-21 18:53 ` Rob Herring
2019-08-27 7:46 ` Linus Walleij
2019-08-05 10:16 ` [PATCH 3/3] pinctrl: mvebu: add additional variant for standalone CP115 Miquel Raynal
2019-08-27 7:49 ` Linus Walleij
2019-08-07 12:47 ` [PATCH 0/3] CP115 pinctrl support Linus Walleij
2019-08-14 8:12 ` Linus Walleij
2019-08-14 12:34 ` Thomas Petazzoni
2019-08-15 8:10 ` Linus Walleij
2019-08-24 11:33 ` Miquel Raynal
2019-08-27 7:50 ` Linus Walleij
2019-08-27 14:24 ` Gregory CLEMENT
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=20190805101607.29811-2-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=antoine.tenart@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jaz@semihalf.com \
--cc=kostap@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ymarkman@marvell.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;
as well as URLs for NNTP newsgroup(s).