From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Krzysztof Adamski <krzysztof.adamski@tieto.com>
Subject: Re: linux-next: manual merge of the gpio tree with the pinctrl tree
Date: Tue, 16 Feb 2016 09:23:48 +0100 [thread overview]
Message-ID: <CAMuHMdW2CVgzX0vvjdrLq4bFwcUvJto_a6JPfXP_NG=VGDoqjw@mail.gmail.com> (raw)
In-Reply-To: <20160216143728.61372efa@canb.auug.org.au>
Hi Stephen,
On Tue, Feb 16, 2016 at 4:37 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next merge of the gpio tree got a conflict in:
>
> drivers/pinctrl/sunxi/pinctrl-sunxi.c
>
> between commit:
>
> be2d107f4433 ("pinctrl: sunxi: Use pin number when calling sunxi_pmx_set")
>
> from the pinctrl tree and commit:
>
> 6cee3821e4e4 ("gpio/pinctrl: sunxi: stop poking around in private vars")
>
> from the gpio tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/pinctrl/sunxi/pinctrl-sunxi.c
> index 96f64a104a62,3e95bfe66a06..000000000000
> --- a/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> +++ b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> @@@ -457,9 -457,8 +457,9 @@@ static int sunxi_pinctrl_gpio_get(struc
> struct sunxi_pinctrl *pctl = gpiochip_get_data(chip);
> u32 reg = sunxi_data_reg(offset);
> u8 index = sunxi_data_offset(offset);
> - u32 set_mux = pctl->desc->irq_read_needs_mux &&
> - test_bit(FLAG_USED_AS_IRQ, &chip->desc[offset].flags);
> + bool set_mux = pctl->desc->irq_read_needs_mux &&
> + gpiochip_line_is_irq(chip, offset);
> + u32 pin = offset + chip->base;
> u32 val;
>
> if (set_mux)
That resolution looks correct to me, but doesn't match your end result
in next-20160216:
u32 set_mux = pctl->desc->irq_read_needs_mux &&
test_bit(FLAG_USED_AS_IRQ, &chip->desc[offset].flags);
u32 pin = offset + chip->base;
I think the end result should be:
bool set_mux = pctl->desc->irq_read_needs_mux &&
gpiochip_line_is_irq(chip, offset);
u32 pin = offset + chip->base;
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-02-16 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 3:37 linux-next: manual merge of the gpio tree with the pinctrl tree Stephen Rothwell
2016-02-16 8:23 ` Geert Uytterhoeven [this message]
2016-02-16 10:16 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2016-09-13 3:15 Stephen Rothwell
2014-10-01 6:01 Stephen Rothwell
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='CAMuHMdW2CVgzX0vvjdrLq4bFwcUvJto_a6JPfXP_NG=VGDoqjw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=krzysztof.adamski@tieto.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).