From: John Crispin <blogic@openwrt.org>
To: Martin Schiller <mschiller@tdt.de>, Jonas Gorski <jogo@openwrt.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
MIPS Mailing List <linux-mips@linux-mips.org>,
Linus Walleij <linus.walleij@linaro.org>,
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>,
Ralf Baechle <ralf@linux-mips.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
"daniel.schwierzeck@gmail.com" <daniel.schwierzeck@gmail.com>
Subject: Re: [PATCH v2 4/4] pinctrl/lantiq: fix up pinmux
Date: Thu, 26 Nov 2015 08:20:32 +0100 [thread overview]
Message-ID: <5656B2C0.6010701@openwrt.org> (raw)
In-Reply-To: <39cc8cd2e53f492f88c45dd256a46b22@TDT-MS.TDTNET.local>
On 26/11/2015 08:15, Martin Schiller wrote:
> On 11/26/2015 at 8:04 AM, John Crispin wrote:
>>
>>
>> On 26/11/2015 07:40, Martin Schiller wrote:
>>> On 11/25/2015 at 11:40 AM, Jonas Gorski wrote:
>>>> Hi
>>>>
>>>> On Wed, Nov 25, 2015 at 11:18 AM, Martin Schiller <mschiller@tdt.de>
>>>> wrote:
>>>>> From: John Crispin <blogic@openwrt.org>
>>>>>
>>>>> This patch is included in the openwrt patchset for several years
>> now
>>>> and needs
>>>>> to go upstream as well. It includes the following changes:
>>>>> 1. Fix up inline function call to xway_mux_apply
>>>>
>>>> This really needs an explanation what is being fixed here.
>>>
>>> I hope John - as the original author of this patch - can explain
>>> why this change is necessary.
>>
>> what change? why am I in Cc: and not To: if an action is required ?
>>
>> John
>
> That change is meant:
> ########################################################################
>> diff --git a/drivers/pinctrl/pinctrl-xway.c b/drivers/pinctrl/pinctrl-
>> xway.c
>> index a064962..f0b1b48 100644
>> --- a/drivers/pinctrl/pinctrl-xway.c
>> +++ b/drivers/pinctrl/pinctrl-xway.c
>> @@ -1496,10 +1496,9 @@ static struct pinctrl_desc xway_pctrl_desc = {
>> .confops= &xway_pinconf_ops,
>> };
>>
>> -static inline int xway_mux_apply(struct pinctrl_dev *pctrldev,
>> +static int mux_apply(struct ltq_pinmux_info *info,
>> int pin, int mux)
>> {
>> -struct ltq_pinmux_info *info = pinctrl_dev_get_drvdata(pctrldev);
>> int port = PORT(pin);
>> u32 alt1_reg = GPIO_ALT1(pin);
>>
>> @@ -1519,6 +1518,14 @@ static inline int xway_mux_apply(struct
>> pinctrl_dev *pctrldev,
>> return 0;
>> }
>>
>> +static inline int xway_mux_apply(struct pinctrl_dev *pctrldev,
>> +int pin, int mux)
>> +{
>> +struct ltq_pinmux_info *info = pinctrl_dev_get_drvdata(pctrldev);
>> +
>> +return mux_apply(info, pin, mux);
>> +}
>> +
>> static const struct ltq_cfg_param xway_cfg_params[] = {
>> {"lantiq,pull",LTQ_PINCONF_PARAM_PULL},
>> {"lantiq,open-drain",LTQ_PINCONF_PARAM_OPEN_DRAIN},
> #######################################################################
>
ok so you picked up a patch and sent it upstream without looking at what
it really does. the patch is simply not ready for upstream. the problem
here is copy & paste inconsistency.
however if we want to resolve this we should either keep the inlines and
just stick to the current code pattern used or we could just assume that
the compiler will be smart enough to to know when to inline and remove
all of them.
i'll leave it up to you to decide and propose your solution as a patch
with an explanation.
John
>>
>>>
>>>>
>>>>> 2. Fix GPIO Setup of GPIO Port3
>>>>
>>>> This change looks fine.
>>>>
>>>>> 3. Implement gpio_chip.to_irq
>>>>
>>>> These are three different changes (two fixes, one new feature) and
>>>> therefore should be split up into three patches.
>>>
>>> As I'm not the author of this patch, I decided to leave it as it is.
>>> But per se you are right, it would be better to split it up.
>>>
>>>>
>>>>> Signed-off-by: John Crispin <blogic@openwrt.org>
>>>>> Signed-off-by: Martin Schiller <mschiller@tdt.de>
>>>>> ---
>>>>
>>>> Also please provide a changelog for your patches here.
>>>
>>> OK.
>>>
>>>>
>>>>> drivers/pinctrl/pinctrl-xway.c | 28 ++++++++++++++++++++++++++--
>>>>> 1 file changed, 26 insertions(+), 2 deletions(-)
>>>>>
>>>>
>>>>
>>>> Jonas
>>>
>>> Martin
>>>
>>>
>
>
next prev parent reply other threads:[~2015-11-26 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 10:18 [PATCH v2 1/4] pinctrl/lantiq: updating devicetree binding description Martin Schiller
2015-11-25 10:18 ` [PATCH v2 2/4] pinctrl/lantiq: introduce new dedicated devicetree bindings Martin Schiller
2015-11-25 10:18 ` [PATCH v2 3/4] pinctrl/lantiq: update devicetree binding in dts file Martin Schiller
2015-11-25 10:18 ` [PATCH v2 4/4] pinctrl/lantiq: fix up pinmux Martin Schiller
2015-11-25 10:40 ` Jonas Gorski
2015-11-26 6:40 ` Martin Schiller
2015-11-26 7:04 ` John Crispin
2015-11-26 7:15 ` Martin Schiller
2015-11-26 7:20 ` John Crispin [this message]
2015-11-26 7:47 ` Martin Schiller
2015-11-25 20:05 ` [PATCH v2 1/4] pinctrl/lantiq: updating devicetree binding description Rob Herring
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=5656B2C0.6010701@openwrt.org \
--to=blogic@openwrt.org \
--cc=daniel.schwierzeck@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jogo@openwrt.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=mschiller@tdt.de \
--cc=pawel.moll@arm.com \
--cc=ralf@linux-mips.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).