From: Joe Perches <joe@perches.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Vignesh R <vigneshr@ti.com>, Yong Li <yong.b.li@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/5] gpio: pca953x: code shrink
Date: Wed, 07 Sep 2016 08:09:33 -0700 [thread overview]
Message-ID: <1473260973.29864.13.camel@perches.com> (raw)
In-Reply-To: <1473259770-26224-2-git-send-email-bgolaszewski@baylibre.com>
On Wed, 2016-09-07 at 16:49 +0200, Bartosz Golaszewski wrote:
> There are multiple places in the driver code where a
> switch (chip->chip_type) is used to determine the proper register
> offset.
>
> Unduplicate the code by adding a simple structure holding the possible
> offsets that differ between the pca953x and pca957x chip families and
> use it to avoid the checks.
[]
> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
[]
> @@ -94,6 +94,24 @@ MODULE_DEVICE_TABLE(acpi, pca953x_acpi_ids);
>
> #define NBANK(chip) DIV_ROUND_UP(chip->gpio_chip.ngpio, BANK_SZ)
>
> +struct pca953x_offset {
> > + int direction;
> > + int output;
> > + int input;
> +};
The struct name seems suboptimal.
Maybe pca95xx_reg_io_config or some such.
> +static const struct pca953x_offset pca953x_offsets = {
> > + .direction = PCA953X_DIRECTION,
> > + .output = PCA953X_OUTPUT,
> > + .input = PCA953X_INPUT,
> +};
> +
> +static const struct pca953x_offset pca957x_offsets = {
> > + .direction = PCA957X_CFG,
> > + .output = PCA957X_OUT,
> > + .input = PCA957X_IN,
> +};
The more naming consistency for #defines would be nice too
at some point.
>
next prev parent reply other threads:[~2016-09-07 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 14:49 [PATCH v4 0/5] gpio: pca953x: code refactoring Bartosz Golaszewski
2016-09-07 14:49 ` [PATCH v4 1/5] gpio: pca953x: code shrink Bartosz Golaszewski
2016-09-07 15:09 ` Joe Perches [this message]
2016-09-07 14:49 ` [PATCH v4 2/5] gpio: pca953x: refactor pca953x_write_regs() Bartosz Golaszewski
2016-09-07 14:49 ` [PATCH v4 3/5] gpio: pca953x: refactor pca953x_read_regs() Bartosz Golaszewski
2016-09-07 14:49 ` [PATCH v4 4/5] gpio: pca953x: remove an unused variable Bartosz Golaszewski
2016-09-07 14:49 ` [PATCH v4 5/5] gpio: pca953x: coding style fixes Bartosz Golaszewski
2016-09-07 15:17 ` Andy Shevchenko
2016-09-07 15:19 ` Bartosz Golaszewski
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=1473260973.29864.13.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vigneshr@ti.com \
--cc=yong.b.li@intel.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