From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: sunxi: fix pin numbers passed to register offset helpers
Date: Thu, 22 May 2014 17:37:24 +0200 [thread overview]
Message-ID: <537E19B4.6070005@free-electrons.com> (raw)
In-Reply-To: <1400772055-3852-1-git-send-email-wens@csie.org>
Hello Chen-Yu,
On 22/05/2014 17:20, Chen-Yu Tsai wrote:
> The pin numbers passed to sunxi_*_reg helpers to get the correct
> registers should be the pin offset for the PIO block, not the
> absolute number we use that is based on the alphanumeric labels
> Allwinner uses.
>
> This patch subtracts .pin_base from the pin number passed to these
> functions, so the driver accesses the correct registers.
Thanks for fixing this bug.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
>
> Hi,
>
> This patch fixes the pinctrl driver failing to set pinmuxes for the R_PIO
> block found on the A31 and A23. The problem was found while working on
> bringing up the A23 SoC. The R_UART pins weren't properly muxed when
> the bootloader didn't use them.
>
> A thank you to Boris who also verified the issue.
>
>
> Cheers,
> ChenYu
>
> ---
> drivers/pinctrl/sunxi/pinctrl-sunxi.c | 26 ++++++++++++++------------
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/pinctrl/sunxi/pinctrl-sunxi.c b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> index f6522b5..59962fa 100644
> --- a/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> +++ b/drivers/pinctrl/sunxi/pinctrl-sunxi.c
> @@ -280,6 +280,7 @@ static int sunxi_pconf_group_set(struct pinctrl_dev *pctldev,
> struct sunxi_pinctrl *pctl = pinctrl_dev_get_drvdata(pctldev);
> struct sunxi_pinctrl_group *g = &pctl->groups[group];
> unsigned long flags;
> + unsigned pin = g->pin - pctl->desc->pin_base;
> u32 val, mask;
> u16 strength;
> u8 dlevel;
> @@ -303,23 +304,23 @@ static int sunxi_pconf_group_set(struct pinctrl_dev *pctldev,
> * 3: 40mA
> */
> dlevel = strength / 10 - 1;
> - val = readl(pctl->membase + sunxi_dlevel_reg(g->pin));
> - mask = DLEVEL_PINS_MASK << sunxi_dlevel_offset(g->pin);
> + val = readl(pctl->membase + sunxi_dlevel_reg(pin));
> + mask = DLEVEL_PINS_MASK << sunxi_dlevel_offset(pin);
> writel((val & ~mask)
> - | dlevel << sunxi_dlevel_offset(g->pin),
> - pctl->membase + sunxi_dlevel_reg(g->pin));
> + | dlevel << sunxi_dlevel_offset(pin),
> + pctl->membase + sunxi_dlevel_reg(pin));
> break;
> case PIN_CONFIG_BIAS_PULL_UP:
> - val = readl(pctl->membase + sunxi_pull_reg(g->pin));
> - mask = PULL_PINS_MASK << sunxi_pull_offset(g->pin);
> - writel((val & ~mask) | 1 << sunxi_pull_offset(g->pin),
> - pctl->membase + sunxi_pull_reg(g->pin));
> + val = readl(pctl->membase + sunxi_pull_reg(pin));
> + mask = PULL_PINS_MASK << sunxi_pull_offset(pin);
> + writel((val & ~mask) | 1 << sunxi_pull_offset(pin),
> + pctl->membase + sunxi_pull_reg(pin));
> break;
> case PIN_CONFIG_BIAS_PULL_DOWN:
> - val = readl(pctl->membase + sunxi_pull_reg(g->pin));
> - mask = PULL_PINS_MASK << sunxi_pull_offset(g->pin);
> - writel((val & ~mask) | 2 << sunxi_pull_offset(g->pin),
> - pctl->membase + sunxi_pull_reg(g->pin));
> + val = readl(pctl->membase + sunxi_pull_reg(pin));
> + mask = PULL_PINS_MASK << sunxi_pull_offset(pin);
> + writel((val & ~mask) | 2 << sunxi_pull_offset(pin),
> + pctl->membase + sunxi_pull_reg(pin));
> break;
> default:
> break;
> @@ -376,6 +377,7 @@ static void sunxi_pmx_set(struct pinctrl_dev *pctldev,
>
> spin_lock_irqsave(&pctl->lock, flags);
>
> + pin -= pctl->desc->pin_base;
> val = readl(pctl->membase + sunxi_mux_reg(pin));
> mask = MUX_PINS_MASK << sunxi_mux_offset(pin);
> writel((val & ~mask) | config << sunxi_mux_offset(pin),
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-22 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 15:20 [PATCH] pinctrl: sunxi: fix pin numbers passed to register offset helpers Chen-Yu Tsai
2014-05-22 15:37 ` Boris BREZILLON [this message]
2014-05-22 22:38 ` Linus Walleij
2014-05-23 7:25 ` Maxime Ripard
2014-05-27 9:27 ` 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=537E19B4.6070005@free-electrons.com \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.