From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 4/4] pinctrl: sh-pfc: Use unsigned int for register/field widths and offsets
Date: Fri, 06 Mar 2015 12:57:29 +0200 [thread overview]
Message-ID: <1895404.raPFfQG332@avalon> (raw)
In-Reply-To: <CAMuHMdWk-XWJz9PswNfkyG6yKctH0Jnf7uPLZ8i1X_umhbO+sA@mail.gmail.com>
Hi Geert,
On Thursday 05 March 2015 10:34:18 Geert Uytterhoeven wrote:
> On Thu, Mar 5, 2015 at 10:20 AM, Laurent Pinchart wrote:
> >> @@ -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) ? :-)
>
> There are just too many variables ;-)
Well, if we need them, we need them :-)
> I usually declare variables in the order of appearance, but try to
> keep variables of the same type together.
>
> Some declarations could move inside the while, e.g.
>
> while (1) {
> const struct pinmux_cfg_reg *config_reg =
> pfc->info->cfg_regs + k;
> unsigned int r_width = config_reg->reg_width;
> unsigned int f_width = config_reg->field_width;
> unsigned int pos = 0, m= 0;
>
> if (!r_width)
> break;
>
> Would you like that?
Yes, but please split pos and m on two different lines :-)
> >> 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;
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 4/4] pinctrl: sh-pfc: Use unsigned int for register/field widths and offsets
Date: Fri, 06 Mar 2015 10:57:29 +0000 [thread overview]
Message-ID: <1895404.raPFfQG332@avalon> (raw)
In-Reply-To: <CAMuHMdWk-XWJz9PswNfkyG6yKctH0Jnf7uPLZ8i1X_umhbO+sA@mail.gmail.com>
Hi Geert,
On Thursday 05 March 2015 10:34:18 Geert Uytterhoeven wrote:
> On Thu, Mar 5, 2015 at 10:20 AM, Laurent Pinchart wrote:
> >> @@ -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) ? :-)
>
> There are just too many variables ;-)
Well, if we need them, we need them :-)
> I usually declare variables in the order of appearance, but try to
> keep variables of the same type together.
>
> Some declarations could move inside the while, e.g.
>
> while (1) {
> const struct pinmux_cfg_reg *config_reg > pfc->info->cfg_regs + k;
> unsigned int r_width = config_reg->reg_width;
> unsigned int f_width = config_reg->field_width;
> unsigned int pos = 0, m= 0;
>
> if (!r_width)
> break;
>
> Would you like that?
Yes, but please split pos and m on two different lines :-)
> >> 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;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-03-06 10:57 UTC|newest]
Thread overview: 48+ 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 ` Geert Uytterhoeven
2015-02-27 17:38 ` [PATCH 1/4] pinctrl: sh-pfc: Do not overwrite bias configuration Geert Uytterhoeven
2015-02-27 17:38 ` Geert Uytterhoeven
2015-03-05 8:57 ` Laurent Pinchart
2015-03-05 8:57 ` Laurent Pinchart
2015-03-06 10:45 ` Linus Walleij
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-02-27 17:38 ` Geert Uytterhoeven
2015-03-05 9:03 ` Laurent Pinchart
2015-03-05 9:03 ` Laurent Pinchart
2015-03-05 9:19 ` Geert Uytterhoeven
2015-03-05 9:19 ` Geert Uytterhoeven
2015-03-05 18:02 ` Geert Uytterhoeven
2015-03-05 18:02 ` Geert Uytterhoeven
2015-03-06 10:55 ` Laurent Pinchart
2015-03-06 10:55 ` Laurent Pinchart
2015-03-06 11:05 ` Laurent Pinchart
2015-03-06 11:05 ` Laurent Pinchart
2015-03-06 11:21 ` Geert Uytterhoeven
2015-03-06 11:21 ` Geert Uytterhoeven
2015-03-06 11:31 ` Laurent Pinchart
2015-03-06 11:31 ` Laurent Pinchart
2015-03-06 10:48 ` Linus Walleij
2015-03-06 10:48 ` Linus Walleij
2015-03-06 11:26 ` Geert Uytterhoeven
2015-03-06 11:26 ` Geert Uytterhoeven
2015-03-06 11:34 ` Laurent Pinchart
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-02-27 17:38 ` Geert Uytterhoeven
2015-03-05 9:14 ` Laurent Pinchart
2015-03-05 9:14 ` Laurent Pinchart
2015-03-05 9:28 ` Geert Uytterhoeven
2015-03-05 9:28 ` Geert Uytterhoeven
2015-03-09 16:37 ` Linus Walleij
2015-03-09 16:37 ` Linus Walleij
2015-03-09 17:56 ` Geert Uytterhoeven
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-02-27 17:38 ` Geert Uytterhoeven
2015-03-05 9:20 ` Laurent Pinchart
2015-03-05 9:20 ` Laurent Pinchart
2015-03-05 9:34 ` Geert Uytterhoeven
2015-03-05 9:34 ` Geert Uytterhoeven
2015-03-06 10:57 ` Laurent Pinchart [this message]
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=1895404.raPFfQG332@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--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 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.