From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Ming Yu <a0282524688@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-rtc@vger.kernel.org,
tmyu0@nuvoton.com, lee@kernel.org, linus.walleij@linaro.org,
brgl@bgdev.pl, andi.shyti@kernel.org, mkl@pengutronix.de,
mailhol.vincent@wanadoo.fr, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, wim@linux-watchdog.org, linux@roeck-us.net,
jdelvare@suse.com, alexandre.belloni@bootlin.com
Subject: Re: [PATCH v3 1/7] mfd: Add core driver for Nuvoton NCT6694
Date: Wed, 11 Dec 2024 17:44:48 +0100 [thread overview]
Message-ID: <47f720f8-90d7-4444-bfde-fb76ec2a2f0f@wanadoo.fr> (raw)
In-Reply-To: <20241210104524.2466586-2-tmyu0@nuvoton.com>
Le 10/12/2024 à 11:45, Ming Yu a écrit :
> The Nuvoton NCT6694 is a peripheral expander with 16 GPIO chips,
> 6 I2C controllers, 2 CANfd controllers, 2 Watchdog timers, ADC,
> PWM, and RTC.
>
> This driver implements USB device functionality and shares the
> chip's peripherals as a child device.
>
> Each child device can use the USB functions nct6694_read_msg()
> and nct6694_write_msg() to issue a command. They can also request
> interrupt that will be called when the USB device receives its
> interrupt pipe.
...
> +int nct6694_read_msg(struct nct6694 *nct6694, u8 mod, u16 offset,
> + u16 length, void *buf)
> +{
> + struct nct6694_cmd_header *cmd_header = nct6694->cmd_header;
> + struct nct6694_response_header *response_header = nct6694->response_header;
> + struct usb_device *udev = nct6694->udev;
> + int tx_len, rx_len, ret;
> +
> + guard(mutex)(&nct6694->access_lock);
Nitpick: This could be moved a few lines below, should it still comply
with your coding style.
> +
> + /* Send command packet to USB device */
> + cmd_header->mod = mod;
> + cmd_header->cmd = offset & 0xFF;
> + cmd_header->sel = (offset >> 8) & 0xFF;
> + cmd_header->hctrl = NCT6694_HCTRL_GET;
> + cmd_header->len = length;
> +
> + ret = usb_bulk_msg(udev, usb_sndbulkpipe(udev, NCT6694_BULK_OUT_EP),
> + cmd_header, NCT6694_CMD_PACKET_SZ, &tx_len,
> + nct6694->timeout);
> + if (ret)
> + return ret;
> +
> + /* Receive response packet from USB device */
> + ret = usb_bulk_msg(udev, usb_rcvbulkpipe(udev, NCT6694_BULK_IN_EP),
> + response_header, NCT6694_CMD_PACKET_SZ, &rx_len,
> + nct6694->timeout);
> + if (ret)
> + return ret;
> +
> + ret = usb_bulk_msg(udev, usb_rcvbulkpipe(udev, NCT6694_BULK_IN_EP),
> + buf, NCT6694_MAX_PACKET_SZ, &rx_len, nct6694->timeout);
> + if (ret)
> + return ret;
> +
> + return nct6694_response_err_handling(nct6694, response_header->sts);
> +}
> +EXPORT_SYMBOL(nct6694_read_msg);
> +
> +int nct6694_write_msg(struct nct6694 *nct6694, u8 mod, u16 offset,
> + u16 length, void *buf)
> +{
> + struct nct6694_cmd_header *cmd_header = nct6694->cmd_header;
> + struct nct6694_response_header *response_header = nct6694->response_header;
> + struct usb_device *udev = nct6694->udev;
> + int tx_len, rx_len, ret;
> +
> + guard(mutex)(&nct6694->access_lock);
Nitpick: This could be moved a few lines below, should it still comply
with your coding style.
> +
> + /* Send command packet to USB device */
Nitpick: double space before */
> + cmd_header->mod = mod;
> + cmd_header->cmd = offset & 0xFF;
> + cmd_header->sel = (offset >> 8) & 0xFF;
> + cmd_header->hctrl = NCT6694_HCTRL_SET;
> + cmd_header->len = length;
...
> +static struct irq_chip nct6694_irq_chip = {
const?
> + .name = "nct6694-irq",
> + .flags = IRQCHIP_SKIP_SET_WAKE,
> + .irq_bus_lock = nct6694_irq_lock,
> + .irq_bus_sync_unlock = nct6694_irq_sync_unlock,
> + .irq_enable = nct6694_irq_enable,
> + .irq_disable = nct6694_irq_disable,
> +};
...
> +static int nct6694_usb_probe(struct usb_interface *iface,
> + const struct usb_device_id *id)
> +{
> + struct usb_device *udev = interface_to_usbdev(iface);
> + struct device *dev = &udev->dev;
> + struct usb_host_interface *interface;
> + struct usb_endpoint_descriptor *int_endpoint;
> + struct nct6694 *nct6694;
> + struct nct6694_cmd_header *cmd_header;
> + struct nct6694_response_header *response_header;
> + int pipe, maxp;
> + int ret;
> +
> + interface = iface->cur_altsetting;
> +
> + int_endpoint = &interface->endpoint[0].desc;
> + if (!usb_endpoint_is_int_in(int_endpoint))
> + return -ENODEV;
> +
> + nct6694 = devm_kzalloc(dev, sizeof(*nct6694), GFP_KERNEL);
> + if (!nct6694)
> + return -ENOMEM;
> +
> + pipe = usb_rcvintpipe(udev, NCT6694_INT_IN_EP);
> + maxp = usb_maxpacket(udev, pipe);
> +
> + cmd_header = devm_kzalloc(dev, sizeof(*cmd_header),
> + GFP_KERNEL);
> + if (!cmd_header)
> + return -ENOMEM;
> +
> + response_header = devm_kzalloc(dev, sizeof(*response_header),
> + GFP_KERNEL);
> + if (!response_header)
> + return -ENOMEM;
> +
> + nct6694->int_buffer = devm_kcalloc(dev, NCT6694_MAX_PACKET_SZ,
> + sizeof(unsigned char), GFP_KERNEL);
Why for cmd_header and response_header we use a temp variable, while
here we update directly nct6694->int_buffer?
It would save a few LoC do remove this temp var.
> + if (!nct6694->int_buffer)
> + return -ENOMEM;
> +
> + nct6694->int_in_urb = usb_alloc_urb(0, GFP_KERNEL);
> + if (!nct6694->int_in_urb)
> + return -ENOMEM;
...
CJ
next prev parent reply other threads:[~2024-12-11 16:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 10:45 [PATCH v3 0/7] Add Nuvoton NCT6694 MFD drivers Ming Yu
2024-12-10 10:45 ` [PATCH v3 1/7] mfd: Add core driver for Nuvoton NCT6694 Ming Yu
2024-12-10 10:57 ` Mateusz Polchlopek
2024-12-11 1:56 ` Jakub Kicinski
2024-12-11 7:16 ` Mateusz Polchlopek
2024-12-10 14:38 ` Krzysztof Kozlowski
2024-12-12 5:27 ` Ming Yu
2024-12-11 16:44 ` Christophe JAILLET [this message]
2024-12-12 7:01 ` Ming Yu
2024-12-12 7:13 ` Christophe JAILLET
2024-12-20 12:45 ` Linus Walleij
2024-12-23 2:04 ` Ming Yu
2024-12-10 10:45 ` [PATCH v3 2/7] gpio: Add Nuvoton NCT6694 GPIO support Ming Yu
2024-12-10 12:46 ` Bartosz Golaszewski
2024-12-12 6:58 ` Ming Yu
2024-12-20 12:41 ` Linus Walleij
2024-12-23 2:02 ` Ming Yu
2024-12-10 10:45 ` [PATCH v3 3/7] i2c: Add Nuvoton NCT6694 I2C support Ming Yu
2024-12-26 0:43 ` Andi Shyti
2024-12-26 2:06 ` Ming Yu
2024-12-26 9:25 ` Andi Shyti
2024-12-10 10:45 ` [PATCH v3 4/7] can: Add Nuvoton NCT6694 CAN support Ming Yu
2024-12-11 9:59 ` Marc Kleine-Budde
2024-12-11 15:25 ` Vincent Mailhol
2024-12-16 6:58 ` Ming Yu
2024-12-16 17:14 ` Vincent Mailhol
2024-12-16 6:21 ` Ming Yu
2024-12-23 9:03 ` Ming Yu
2024-12-10 10:45 ` [PATCH v3 5/7] watchdog: Add Nuvoton NCT6694 WDT support Ming Yu
2024-12-10 15:22 ` Guenter Roeck
2024-12-12 6:26 ` Ming Yu
2024-12-10 10:45 ` [PATCH v3 6/7] hwmon: Add Nuvoton NCT6694 HWMON support Ming Yu
2024-12-10 15:58 ` Guenter Roeck
2024-12-12 7:09 ` Ming Yu
2024-12-12 16:10 ` Vincent Mailhol
2024-12-16 7:04 ` Ming Yu
2024-12-10 10:45 ` [PATCH v3 7/7] rtc: Add Nuvoton NCT6694 RTC support Ming Yu
2024-12-16 10:41 ` Alexandre Belloni
2024-12-23 1:50 ` Ming Yu
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=47f720f8-90d7-4444-bfde-fb76ec2a2f0f@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=a0282524688@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tmyu0@nuvoton.com \
--cc=wim@linux-watchdog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox