From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-gpio@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 4/4] pinctrl: sh-pfc: Use unsigned int for register/field widths and offsets
Date: Thu, 05 Mar 2015 11:20:55 +0200 [thread overview]
Message-ID: <9833485.4LcIhc9qJb@avalon> (raw)
In-Reply-To: <1425058685-12956-5-git-send-email-geert+renesas@glider.be>
Hi Geert,
Thank you for the patch.
On Friday 27 February 2015 18:38:05 Geert Uytterhoeven wrote:
> As register and field widths and offsets are in the range 0..32, use
> unsigned int (mostly replacing unsigned long) to store them in local
> variables and for passing them around.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/pinctrl/sh-pfc/core.c | 25 ++++++++++++-------------
> drivers/pinctrl/sh-pfc/core.h | 4 ++--
> drivers/pinctrl/sh-pfc/gpio.c | 6 ++----
> 3 files changed, 16 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/core.c b/drivers/pinctrl/sh-pfc/core.c
> index 1758043cfcec253b..0350c64229ea0734 100644
> --- a/drivers/pinctrl/sh-pfc/core.c
> +++ b/drivers/pinctrl/sh-pfc/core.c
> @@ -144,7 +144,7 @@ static int sh_pfc_enum_in_range(u16 enum_id, const
> struct pinmux_range *r) return 1;
> }
>
> -u32 sh_pfc_read_raw_reg(void __iomem *mapped_reg, unsigned long reg_width)
> +u32 sh_pfc_read_raw_reg(void __iomem *mapped_reg, unsigned int reg_width)
> {
> switch (reg_width) {
> case 8:
> @@ -159,7 +159,7 @@ u32 sh_pfc_read_raw_reg(void __iomem *mapped_reg,
> unsigned long reg_width) return 0;
> }
>
> -void sh_pfc_write_raw_reg(void __iomem *mapped_reg, unsigned long
> reg_width,
> +void sh_pfc_write_raw_reg(void __iomem *mapped_reg, unsigned
> int reg_width, u32 data)
> {
> switch (reg_width) {
> @@ -179,9 +179,9 @@ void sh_pfc_write_raw_reg(void __iomem *mapped_reg,
> unsigned long reg_width,
>
> static void sh_pfc_config_reg_helper(struct sh_pfc *pfc,
> const struct pinmux_cfg_reg *crp,
> - unsigned long in_pos,
> + unsigned int in_pos,
> void __iomem **mapped_regp, u32 *maskp,
> - unsigned long *posp)
> + unsigned int *posp)
> {
> unsigned int k;
>
> @@ -200,15 +200,15 @@ static void sh_pfc_config_reg_helper(struct sh_pfc
> *pfc,
>
> static void sh_pfc_write_config_reg(struct sh_pfc *pfc,
> const struct pinmux_cfg_reg *crp,
> - unsigned long field, u32 value)
> + unsigned int field, u32 value)
> {
> void __iomem *mapped_reg;
> - unsigned long pos;
> + unsigned int pos;
> u32 mask, data;
>
> sh_pfc_config_reg_helper(pfc, crp, field, &mapped_reg, &mask, &pos);
>
> - dev_dbg(pfc->dev, "write_reg addr = %lx, value = 0x%x, field = %ld, "
> + dev_dbg(pfc->dev, "write_reg addr = %lx, value = 0x%x, field = %u, "
> "r_width = %u, f_width = %u\n",
> crp->reg, value, field, crp->reg_width, crp->field_width);
>
> @@ -228,12 +228,11 @@ static void sh_pfc_write_config_reg(struct sh_pfc
> *pfc, }
>
> static int sh_pfc_get_config_reg(struct sh_pfc *pfc, u16 enum_id,
> - const struct pinmux_cfg_reg **crp, int *fieldp,
> - u32 *valuep)
> + const struct pinmux_cfg_reg **crp,
> + unsigned int *fieldp, u32 *valuep)
> {
> const struct pinmux_cfg_reg *config_reg;
> - unsigned long r_width, f_width, curr_width;
> - unsigned int k, m, pos, bit_pos;
> + unsigned int r_width, f_width, curr_width, k, m, pos, bit_pos;
I find declaring multiple variables per line quite difficult to read. I know
it's the current coding style in this driver, but I'd like to fix it at some
point. I would move to one variable per line as part of this patch for the
code that it touches. Alternatively could you at least not make it worse (here
and below) ? :-)
> u32 ncomb, n;
>
> k = 0;
> @@ -300,9 +299,9 @@ int sh_pfc_config_mux(struct sh_pfc *pfc, unsigned mark,
> int pinmux_type) const struct pinmux_cfg_reg *cr = NULL;
> u16 enum_id;
> const struct pinmux_range *range;
> - int in_range, pos, field;
> + int in_range, pos, ret;
> + unsigned int field;
> u32 value;
> - int ret;
>
> switch (pinmux_type) {
> case PINMUX_TYPE_GPIO:
> diff --git a/drivers/pinctrl/sh-pfc/core.h b/drivers/pinctrl/sh-pfc/core.h
> index 8a10dd50ccdd2e0c..6dc8a6fc27468b39 100644
> --- a/drivers/pinctrl/sh-pfc/core.h
> +++ b/drivers/pinctrl/sh-pfc/core.h
> @@ -57,8 +57,8 @@ int sh_pfc_unregister_gpiochip(struct sh_pfc *pfc);
> int sh_pfc_register_pinctrl(struct sh_pfc *pfc);
> int sh_pfc_unregister_pinctrl(struct sh_pfc *pfc);
>
> -u32 sh_pfc_read_raw_reg(void __iomem *mapped_reg, unsigned long reg_width);
> -void sh_pfc_write_raw_reg(void __iomem *mapped_reg, unsigned long
> reg_width, +u32 sh_pfc_read_raw_reg(void __iomem *mapped_reg, unsigned int
> reg_width); +void sh_pfc_write_raw_reg(void __iomem *mapped_reg, unsigned
> int reg_width, u32 data);
>
> int sh_pfc_get_pin_index(struct sh_pfc *pfc, unsigned int pin);
> diff --git a/drivers/pinctrl/sh-pfc/gpio.c b/drivers/pinctrl/sh-pfc/gpio.c
> index f2bb7d7398cdfc24..b68d24099593d3b8 100644
> --- a/drivers/pinctrl/sh-pfc/gpio.c
> +++ b/drivers/pinctrl/sh-pfc/gpio.c
> @@ -153,8 +153,7 @@ static void gpio_pin_set_value(struct sh_pfc_chip *chip,
> unsigned offset, int value)
> {
> struct sh_pfc_gpio_data_reg *reg;
> - unsigned long pos;
> - unsigned int bit;
> + unsigned int pos, bit;
>
> gpio_get_data_reg(chip, offset, ®, &bit);
>
> @@ -185,8 +184,7 @@ static int gpio_pin_get(struct gpio_chip *gc, unsigned
> offset) {
> struct sh_pfc_chip *chip = gpio_to_pfc_chip(gc);
> struct sh_pfc_gpio_data_reg *reg;
> - unsigned long pos;
> - unsigned int bit;
> + unsigned int pos, bit;
>
> gpio_get_data_reg(chip, offset, ®, &bit);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-03-05 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 17:38 [PATCH 0/4] pinctrl: sh-pfc: Fix pin bias and cleanups Geert Uytterhoeven
2015-02-27 17:38 ` [PATCH 1/4] pinctrl: sh-pfc: Do not overwrite bias configuration Geert Uytterhoeven
2015-03-05 8:57 ` Laurent Pinchart
2015-03-06 10:45 ` Linus Walleij
2015-02-27 17:38 ` [PATCH 2/4] pinctrl: sh-pfc: Store register/field widths in u8 instead of unsigned long Geert Uytterhoeven
2015-03-05 9:03 ` Laurent Pinchart
2015-03-05 9:19 ` Geert Uytterhoeven
2015-03-05 18:02 ` Geert Uytterhoeven
2015-03-06 10:55 ` Laurent Pinchart
2015-03-06 11:05 ` Laurent Pinchart
2015-03-06 11:21 ` Geert Uytterhoeven
2015-03-06 11:31 ` Laurent Pinchart
2015-03-06 10:48 ` Linus Walleij
2015-03-06 11:26 ` Geert Uytterhoeven
2015-03-06 11:34 ` Laurent Pinchart
2015-02-27 17:38 ` [PATCH 3/4] pinctrl: sh-pfc: Use u32 to store register data Geert Uytterhoeven
2015-03-05 9:14 ` Laurent Pinchart
2015-03-05 9:28 ` Geert Uytterhoeven
2015-03-09 16:37 ` Linus Walleij
2015-03-09 17:56 ` Geert Uytterhoeven
2015-02-27 17:38 ` [PATCH 4/4] pinctrl: sh-pfc: Use unsigned int for register/field widths and offsets Geert Uytterhoeven
2015-03-05 9:20 ` Laurent Pinchart [this message]
2015-03-05 9:34 ` Geert Uytterhoeven
2015-03-06 10:57 ` Laurent Pinchart
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=9833485.4LcIhc9qJb@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).