From: Oliver Neukum <oneukum@suse.com>
To: Wentong Wu <wentong.wu@intel.com>,
gregkh@linuxfoundation.org, 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,
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
Cc: zhifeng.wang@intel.com
Subject: Re: [PATCH v11 1/4] usb: Add support for Intel LJCA device
Date: Thu, 31 Aug 2023 13:16:25 +0200 [thread overview]
Message-ID: <9b2265a3-e10d-ee85-db48-45c75dd4b89f@suse.com> (raw)
In-Reply-To: <1693284848-29269-2-git-send-email-wentong.wu@intel.com>
On 29.08.23 06:54, Wentong Wu wrote:
> +static void ljca_recv(struct urb *urb)
> +{
> + struct ljca_msg *header = urb->transfer_buffer;
> + struct ljca_adapter *adap = urb->context;
> + int ret;
> +
> + if (urb->status) {
> + /* sync/async unlink faults aren't errors */
> + if (urb->status == -ENOENT || urb->status == -ECONNRESET ||
> + urb->status == -ESHUTDOWN)
> + return;
> +
> + dev_err(adap->dev, "recv urb error: %d\n", urb->status);
> + goto resubmit;
> + }
> +
> + if (header->len + sizeof(*header) != urb->actual_length)
> + goto resubmit;
> +
> + if (header->flags & LJCA_ACK_FLAG)
> + ljca_handle_cmd_ack(adap, header);
> + else
> + ljca_handle_event(adap, header);
> +
> +resubmit:
> + ret = usb_submit_urb(urb, GFP_ATOMIC);
> + if (ret)
> + dev_err(adap->dev, "resubmit recv urb error %d\n", ret);
This will detect an error if you get an unlucky timing with ljca_suspend().
The correct test would be:
if (ret && ret != -EPERM)
HTH
Oliver
next prev parent reply other threads:[~2023-08-31 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 4:54 [PATCH v11 0/4] Add Intel LJCA device driver Wentong Wu
2023-08-29 4:54 ` [PATCH v11 1/4] usb: Add support for Intel LJCA device Wentong Wu
2023-08-31 11:16 ` Oliver Neukum [this message]
2023-08-31 12:39 ` Wu, Wentong
2023-08-29 4:54 ` [PATCH v11 2/4] i2c: Add support for Intel LJCA USB I2C driver Wentong Wu
2023-08-30 19:12 ` Wolfram Sang
2023-08-30 20:08 ` Wu, Wentong
2023-08-29 4:54 ` [PATCH v11 3/4] spi: Add support for Intel LJCA USB SPI driver Wentong Wu
2023-08-29 4:54 ` [PATCH v11 4/4] gpio: update Intel LJCA USB GPIO driver Wentong Wu
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=9b2265a3-e10d-ee85-db48-45c75dd4b89f@suse.com \
--to=oneukum@suse.com \
--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=gregkh@linuxfoundation.org \
--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=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).