From: Stefan Wahren <stefan.wahren@i2se.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Eric Anholt <eric@anholt.net>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
linux-gpio@vger.kernel.org, Lukas Wunner <lukas@wunner.de>,
Peter Robinson <pbrobinson@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC V2 1/4] pinctrl: bcm2835: declare pin config as generic
Date: Mon, 21 Jan 2019 08:11:22 +0100 [thread overview]
Message-ID: <1548054685-3781-2-git-send-email-stefan.wahren@i2se.com> (raw)
In-Reply-To: <1548054685-3781-1-git-send-email-stefan.wahren@i2se.com>
Since commit 0de704955ee44 ("pinctrl: bcm2835: Add support for
generic pinctrl binding") this driver is capable to use the generic
interface. So declare this accordingly.
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
---
drivers/pinctrl/bcm/pinctrl-bcm2835.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pinctrl/bcm/pinctrl-bcm2835.c b/drivers/pinctrl/bcm/pinctrl-bcm2835.c
index f180aa4..19eb4fd 100644
--- a/drivers/pinctrl/bcm/pinctrl-bcm2835.c
+++ b/drivers/pinctrl/bcm/pinctrl-bcm2835.c
@@ -969,6 +969,7 @@ static int bcm2835_pinconf_set(struct pinctrl_dev *pctldev,
}
static const struct pinconf_ops bcm2835_pinconf_ops = {
+ .is_generic = true,
.pin_config_get = bcm2835_pinconf_get,
.pin_config_set = bcm2835_pinconf_set,
};
--
2.7.4
next prev parent reply other threads:[~2019-01-21 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 7:11 [PATCH RFC V2 0/4] pinctrl: bcm2835: improve libgpiod output Stefan Wahren
2019-01-21 7:11 ` Stefan Wahren [this message]
2019-01-28 8:02 ` [PATCH RFC V2 1/4] pinctrl: bcm2835: declare pin config as generic Linus Walleij
2019-01-21 7:11 ` [PATCH RFC V2 2/4] pinctrl: bcm2835: Direct GPIO config changes to generic pinctrl Stefan Wahren
2019-01-21 7:11 ` [PATCH RFC V2 3/4] pinctrl: bcm2835: activate strict mux mode Stefan Wahren
[not found] ` <20190121073419.iosy3bd6tcnexya7@wunner.de>
2019-01-21 9:57 ` Stefan Wahren
2019-01-21 7:11 ` [PATCH RFC V2 4/4] gpiolib: Take MUX usage into account Stefan Wahren
2019-01-28 9:06 ` Linus Walleij
2019-01-28 8:06 ` [PATCH RFC V2 0/4] pinctrl: bcm2835: improve libgpiod output Linus Walleij
2019-01-28 9:23 ` Stefan Wahren
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=1548054685-3781-2-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bgolaszewski@baylibre.com \
--cc=eric@anholt.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=pbrobinson@gmail.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).