From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 10/12] gpio: ts4900: Use of_device_get_match_data()
Date: Mon, 30 Apr 2018 09:38:17 +0200 [thread overview]
Message-ID: <20180430073819.31827-10-thierry.reding@gmail.com> (raw)
In-Reply-To: <20180430073819.31827-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Use of_device_get_match_data() instead of open-coding it.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/gpio/gpio-ts4900.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/gpio/gpio-ts4900.c b/drivers/gpio/gpio-ts4900.c
index 5bd21725e604..1da8d0586329 100644
--- a/drivers/gpio/gpio-ts4900.c
+++ b/drivers/gpio/gpio-ts4900.c
@@ -128,15 +128,10 @@ MODULE_DEVICE_TABLE(of, ts4900_gpio_of_match_table);
static int ts4900_gpio_probe(struct i2c_client *client,
const struct i2c_device_id *id)
{
- const struct of_device_id *match;
struct ts4900_gpio_priv *priv;
u32 ngpio;
int ret;
- match = of_match_device(ts4900_gpio_of_match_table, &client->dev);
- if (!match)
- return -EINVAL;
-
if (of_property_read_u32(client->dev.of_node, "ngpios", &ngpio))
ngpio = DEFAULT_PIN_NUMBER;
@@ -148,7 +143,7 @@ static int ts4900_gpio_probe(struct i2c_client *client,
priv->gpio_chip.label = "ts4900-gpio";
priv->gpio_chip.ngpio = ngpio;
priv->gpio_chip.parent = &client->dev;
- priv->input_bit = (uintptr_t)match->data;
+ priv->input_bit = (uintptr_t)of_device_get_match_data(&client->dev);
priv->regmap = devm_regmap_init_i2c(client, &ts4900_regmap_config);
if (IS_ERR(priv->regmap)) {
--
2.17.0
next prev parent reply other threads:[~2018-04-30 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 7:38 [PATCH 01/12] gpio: 74xx-mmio: " Thierry Reding
2018-04-30 7:38 ` [PATCH 02/12] gpio: dwapb: " Thierry Reding
2018-04-30 7:38 ` [PATCH 03/12] gpio: ge: " Thierry Reding
2018-04-30 7:38 ` [PATCH 04/12] gpio: ingenic: " Thierry Reding
2018-04-30 7:38 ` [PATCH 05/12] gpio: mxs: " Thierry Reding
2018-04-30 7:38 ` [PATCH 06/12] gpio: palmas: " Thierry Reding
2018-04-30 7:38 ` [PATCH 07/12] gpio: pca953x: " Thierry Reding
2018-04-30 7:38 ` [PATCH 08/12] gpio: pxa: " Thierry Reding
2018-04-30 7:38 ` [PATCH 09/12] gpio: syscon: " Thierry Reding
2018-04-30 7:38 ` Thierry Reding [this message]
2018-04-30 7:38 ` [PATCH 11/12] gpio: vf610: " Thierry Reding
2018-04-30 7:38 ` [PATCH 12/12] gpio: xlp: " Thierry Reding
2018-05-02 12:44 ` [PATCH 01/12] gpio: 74xx-mmio: " Linus Walleij
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=20180430073819.31827-10-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome