From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>,
Linus Walleij <linus.walleij@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@sonymobile.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v5 3/4] pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver
Date: Tue, 21 Oct 2014 19:15:52 +0100 [thread overview]
Message-ID: <5446A2D8.3070204@linaro.org> (raw)
In-Reply-To: <1412181058-29179-4-git-send-email-iivanov@mm-sol.com>
Hi Ivan,
Just realized that this patch can generate compiler errors due to 3.18
changes in pinmux_ops struct and gpiochip_remove returns void now.
Same with drivers/pinctrl/qcom/pinctrl-spmi-pmic-mpp.c
On 01/10/14 17:30, Ivan T. Ivanov wrote:
> + .enable = pmic_gpio_pinmux_enable,
> +};
>
> +static int pmic_gpio_remove(struct platform_device *pdev)
> +{
> + struct pmic_gpio_state *state = platform_get_drvdata(pdev);
> + int ret;
> +
> + ret = gpiochip_remove(&state->chip);
> + if (ret < 0)
> + return ret;
diff --git a/drivers/pinctrl/qcom/pinctrl-spmi-pmic-gpio.c
b/drivers/pinctrl/qcom/pinctrl-spmi-pmic-gpio.c
index 493f0d3..0d69758 100644
--- a/drivers/pinctrl/qcom/pinctrl-spmi-pmic-gpio.c
+++ b/drivers/pinctrl/qcom/pinctrl-spmi-pmic-gpio.c
@@ -378,7 +378,7 @@ static const struct pinmux_ops pmic_gpio_pinmux_ops = {
.get_functions_count = pmic_gpio_get_functions_count,
.get_function_name = pmic_gpio_get_function_name,
.get_function_groups = pmic_gpio_get_function_groups,
- .enable = pmic_gpio_pinmux_enable,
+ .set_mux = pmic_gpio_pinmux_enable,
};
static int pmic_gpio_config_get(struct pinctrl_dev *pctldev,
@@ -907,12 +907,8 @@ err_chip:
static int pmic_gpio_remove(struct platform_device *pdev)
{
struct pmic_gpio_state *state = platform_get_drvdata(pdev);
- int ret;
-
- ret = gpiochip_remove(&state->chip);
- if (ret < 0)
- return ret;
+ gpiochip_remove(&state->chip);
pinctrl_unregister(state->ctrl);
return 0;
Thanks,
srini
next prev parent reply other threads:[~2014-10-21 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 16:30 [PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers Ivan T. Ivanov
[not found] ` <1412181058-29179-1-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2014-10-01 16:30 ` [PATCH v5 1/4] pinctrl: Device tree bindings for Qualcomm PMIC GPIO block Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 4/4] pinctrl: Qualcomm SPMI PMIC MPP pin controller driver Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 2/4] pinctrl: Device tree bindings for Qualcomm PMIC MPP block Ivan T. Ivanov
2014-10-01 16:30 ` [PATCH v5 3/4] pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver Ivan T. Ivanov
2014-10-21 18:15 ` Srinivas Kandagatla [this message]
2014-10-22 9:35 ` Ivan T. Ivanov
2014-10-03 23:53 ` [PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers Bjorn Andersson
[not found] ` <20141003235320.GC28481-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>
2014-10-07 11:55 ` Ivan T. Ivanov
2014-10-21 10:59 ` Linus Walleij
2014-10-21 11:41 ` Ivan T. Ivanov
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=5446A2D8.3070204@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=iivanov@mm-sol.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).