From: Greg KH <gregkh@linuxfoundation.org>
To: Wentong Wu <wentong.wu@intel.com>
Cc: arnd@arndb.de, mka@chromium.org, oneukum@suse.com,
lee@kernel.org, wsa@kernel.org, kfting@nuvoton.com,
broonie@kernel.org, linus.walleij@linaro.org,
hdegoede@redhat.com, maz@kernel.org, brgl@bgdev.pl,
linux-usb@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-spi@vger.kernel.org, linux-gpio@vger.kernel.org,
andriy.shevchenko@linux.intel.com,
heikki.krogerus@linux.intel.com, andi.shyti@linux.intel.com,
sakari.ailus@linux.intel.com, bartosz.golaszewski@linaro.org,
srinivas.pandruvada@intel.com, zhifeng.wang@intel.com
Subject: Re: [PATCH v19 4/4] gpio: update Intel LJCA USB GPIO driver
Date: Thu, 28 Sep 2023 16:17:05 +0200 [thread overview]
Message-ID: <2023092804-cider-viscosity-03b6@gregkh> (raw)
In-Reply-To: <1694890416-14409-5-git-send-email-wentong.wu@intel.com>
On Sun, Sep 17, 2023 at 02:53:36AM +0800, Wentong Wu wrote:
> This driver communicate with LJCA GPIO module with specific
> protocol through interfaces exported by LJCA USB driver.
> Update the driver according to LJCA USB driver's changes.
>
> Signed-off-by: Wentong Wu <wentong.wu@intel.com>
> Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Acked-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> Tested-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/gpio/Kconfig | 4 +-
> drivers/gpio/gpio-ljca.c | 246 +++++++++++++++++++++++++++--------------------
> 2 files changed, 145 insertions(+), 105 deletions(-)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 673bafb..8d5b6c3 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -1312,9 +1312,9 @@ config GPIO_KEMPLD
>
> config GPIO_LJCA
> tristate "INTEL La Jolla Cove Adapter GPIO support"
> - depends on MFD_LJCA
> + depends on USB_LJCA
> select GPIOLIB_IRQCHIP
> - default MFD_LJCA
> + default USB_LJCA
> help
> Select this option to enable GPIO driver for the INTEL
> La Jolla Cove Adapter (LJCA) board.
> diff --git a/drivers/gpio/gpio-ljca.c b/drivers/gpio/gpio-ljca.c
> index 87863f0..7fae26d 100644
> --- a/drivers/gpio/gpio-ljca.c
> +++ b/drivers/gpio/gpio-ljca.c
> @@ -6,6 +6,7 @@
> */
>
> #include <linux/acpi.h>
> +#include <linux/auxiliary_bus.h>
> #include <linux/bitfield.h>
> #include <linux/bitops.h>
> #include <linux/dev_printk.h>
> @@ -13,19 +14,18 @@
> #include <linux/irq.h>
> #include <linux/kernel.h>
> #include <linux/kref.h>
> -#include <linux/mfd/ljca.h>
> #include <linux/module.h>
> -#include <linux/platform_device.h>
> #include <linux/slab.h>
> #include <linux/types.h>
> +#include <linux/usb/ljca.h>
>
> /* GPIO commands */
> -#define LJCA_GPIO_CONFIG 1
> -#define LJCA_GPIO_READ 2
> -#define LJCA_GPIO_WRITE 3
> -#define LJCA_GPIO_INT_EVENT 4
> -#define LJCA_GPIO_INT_MASK 5
> -#define LJCA_GPIO_INT_UNMASK 6
> +#define LJCA_GPIO_CONFIG 1
> +#define LJCA_GPIO_READ 2
> +#define LJCA_GPIO_WRITE 3
> +#define LJCA_GPIO_INT_EVENT 4
> +#define LJCA_GPIO_INT_MASK 5
> +#define LJCA_GPIO_INT_UNMASK 6
Why are you changing whitespace for no good reason?
Please don't do that, it makes finding the actual changes in this driver
impossible to notice and review.
>
> #define LJCA_GPIO_CONF_DISABLE BIT(0)
> #define LJCA_GPIO_CONF_INPUT BIT(1)
> @@ -36,45 +36,49 @@
> #define LJCA_GPIO_CONF_INTERRUPT BIT(6)
> #define LJCA_GPIO_INT_TYPE BIT(7)
>
> -#define LJCA_GPIO_CONF_EDGE FIELD_PREP(LJCA_GPIO_INT_TYPE, 1)
> -#define LJCA_GPIO_CONF_LEVEL FIELD_PREP(LJCA_GPIO_INT_TYPE, 0)
> +#define LJCA_GPIO_CONF_EDGE FIELD_PREP(LJCA_GPIO_INT_TYPE, 1)
> +#define LJCA_GPIO_CONF_LEVEL FIELD_PREP(LJCA_GPIO_INT_TYPE, 0)
>
> /* Intentional overlap with PULLUP / PULLDOWN */
> -#define LJCA_GPIO_CONF_SET BIT(3)
> -#define LJCA_GPIO_CONF_CLR BIT(4)
> +#define LJCA_GPIO_CONF_SET BIT(3)
> +#define LJCA_GPIO_CONF_CLR BIT(4)
>
> -struct gpio_op {
> +#define LJCA_GPIO_BUF_SIZE 60u
Why "u"? What requires that?
Odd, sorry, I know people are just getting tired of the constant churn
here, but really, you know better than making changes that are not
needed, or not documented.
greg k-h
next prev parent reply other threads:[~2023-09-28 14:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 18:53 [PATCH v19 0/4] Add Intel LJCA device driver Wentong Wu
2023-09-16 18:53 ` [PATCH v19 1/4] usb: Add support for Intel LJCA device Wentong Wu
2023-09-28 14:36 ` Greg KH
2023-09-29 11:31 ` Wu, Wentong
2023-10-02 11:30 ` Greg KH
2023-10-03 2:51 ` Wu, Wentong
2023-10-06 13:07 ` Wu, Wentong
2023-09-16 18:53 ` [PATCH v19 2/4] i2c: Add support for Intel LJCA USB I2C driver Wentong Wu
2023-09-29 7:51 ` Wolfram Sang
2023-09-29 16:11 ` Wu, Wentong
2023-09-29 20:10 ` Wolfram Sang
2023-09-16 18:53 ` [PATCH v19 3/4] spi: Add support for Intel LJCA USB SPI driver Wentong Wu
2023-09-16 18:53 ` [PATCH v19 4/4] gpio: update Intel LJCA USB GPIO driver Wentong Wu
2023-09-28 14:17 ` Greg KH [this message]
2023-09-29 11:33 ` Wu, Wentong
2023-09-17 10:37 ` [PATCH v19 0/4] Add Intel LJCA device driver Marc Zyngier
2023-09-17 10:42 ` Greg KH
2023-09-17 11:26 ` Hans de Goede
2023-09-28 10:18 ` Oliver Neukum
2023-09-28 12:20 ` Hans de Goede
2023-09-28 12:24 ` Greg KH
2023-09-28 12:43 ` Mark Brown
2023-09-28 12:28 ` Andi Shyti
2023-09-28 13:56 ` Bartosz Golaszewski
2023-09-18 3:08 ` Wu, Wentong
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=2023092804-cider-viscosity-03b6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andi.shyti@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=kfting@nuvoton.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mka@chromium.org \
--cc=oneukum@suse.com \
--cc=sakari.ailus@linux.intel.com \
--cc=srinivas.pandruvada@intel.com \
--cc=wentong.wu@intel.com \
--cc=wsa@kernel.org \
--cc=zhifeng.wang@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;
as well as URLs for NNTP newsgroup(s).