From: Jimmy Assarsson <jimmyassarsson@gmail.com>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Arunachalam Santhanam <arunachalam.santhanam@in.bosch.com>,
linux-kernel@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org
Subject: Re: [RESEND v12] can: usb: etas_es58X: add support for ETAS ES58X CAN USB interfaces
Date: Tue, 9 Mar 2021 18:27:41 +0100 [thread overview]
Message-ID: <45c0b0cc-bfd6-5180-7ad9-51eebc9de3c9@gmail.com> (raw)
In-Reply-To: <20210309120946.1640-2-mailhol.vincent@wanadoo.fr>
Hi Vincent,
On 2021-03-09 13:09, Vincent Mailhol wrote:
> This driver supports the ES581.4, ES582.1 and ES584.1 interfaces from
> ETAS GmbH (https://www.etas.com/en/products/es58x.php).
...
> diff --git a/drivers/net/can/usb/etas_es58x/es58x_core.c b/drivers/net/can/usb/etas_es58x/es58x_core.c
> new file mode 100644
> index 000000000000..31f907a7b75f
> --- /dev/null
> +++ b/drivers/net/can/usb/etas_es58x/es58x_core.c
...
> +/**
> + * es58x_add_skb_idx() - Increment an index of the loopback FIFO.
> + * @priv: ES58X private parameters related to the network device.
> + * @idx: address of the index to be incremented.
> + * @a: the increment. Must be positive and less or equal to
> + * @priv->can.echo_skb_max.
> + *
> + * Do a modulus addition: set *@idx to (*@idx + @a) %
> + * @priv->can.echo_skb_max.
> + *
> + * Rationale: the modulus operator % takes a decent amount of CPU
> + * cycles (c.f. other division functions such as
> + * include/linux/math64.h:iter_div_u64_rem()).
> + */
> +static __always_inline void es58x_add_skb_idx(struct es58x_priv *priv,
> + u16 *idx, u16 a)
Never used?
...
> +/**
> + * es58x_get_product_info() - Get the product information and print them.
> + * @es58x_dev: ES58X device.
> + *
> + * Do a synchronous call to get the product information.
> + *
> + * Return: zero on success, errno when any error occurs.
> + */
> +static int es58x_get_product_info(struct es58x_device *es58x_dev)
> +{
> + struct usb_device *udev = es58x_dev->udev;
> + const int es58x_prod_info_idx = 6;
> + /* Empirical tests show a prod_info length of maximum 83,
> + * below should be more than enough.
> + */
> + const size_t prod_info_len = 127;
> + char *prod_info;
> + int ret;
> +
> + prod_info = kmalloc(prod_info_len, GFP_KERNEL);
> + if (!prod_info)
> + return -ENOMEM;
> +
> + ret = usb_string(udev, es58x_prod_info_idx, prod_info, prod_info_len);
> + if (ret < 0) {
> + dev_err(es58x_dev->dev,
> + "%s: Could not read the product info: %pe\n",
> + __func__, ERR_PTR(ret));
Missing free
> + return ret;
> + } else if (ret >= prod_info_len - 1) {
> + dev_warn(es58x_dev->dev,
> + "%s: Buffer is too small, result might be truncated\n",
> + __func__);
> + }
> + dev_info(es58x_dev->dev, "Product info: %s\n", prod_info);
> + kfree(prod_info);
> +
> + return 0;
> +}
Regards,
jimmy
next prev parent reply other threads:[~2021-03-09 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 12:09 [RESEND v12 0/1] Introducing " Vincent Mailhol
2021-03-09 12:09 ` [RESEND v12] can: usb: etas_es58X: add support for " Vincent Mailhol
2021-03-09 17:27 ` Jimmy Assarsson [this message]
2021-03-09 18:11 ` Vincent MAILHOL
2021-03-09 18:18 ` Vincent MAILHOL
2021-03-09 18:22 ` Jimmy Assarsson
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=45c0b0cc-bfd6-5180-7ad9-51eebc9de3c9@gmail.com \
--to=jimmyassarsson@gmail.com \
--cc=arunachalam.santhanam@in.bosch.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
/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
all inboxes | Powered by JetHome®