All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christian Engelmayer <christian.engelmayer@frequentis.com>
Cc: Forest Bond <forest.bond@rapidrollout.com>,
	Daniel Ritz <daniel.ritz@gmx.ch>,
	linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] Input: usbtouchscreen - separate report and transmit buffer size handling
Date: Tue, 15 Oct 2013 23:29:02 -0700	[thread overview]
Message-ID: <20131016062902.GA4282@core.coreip.homeip.net> (raw)
In-Reply-To: <20131015165000.5987a916@frequentis.com>

Hi Christian,

On Tue, Oct 15, 2013 at 04:50:00PM +0200, Christian Engelmayer wrote:
> This patch supports the separate handling of the USB transfer buffer length
> and the length of the buffer used for multi packet support. The USB transfer
> size can now be explicitly configured via the device_info record. Otherwise
> it defaults to the configured report packet size as before. For devices
> supporting multiple report or diagnostic packets, the USB transfer size is
> now reduced to the USB endpoints wMaxPacketSize if not explicitly set.
> 
> This fixes an issue where event reporting can be delayed for an arbitrary
> time for multi packet devices. For instance the report size for eGalax devices
> is defined to the 16 byte maximum diagnostic packet size as opposed to the 5
> byte report packet size. In case the driver requests 16 byte from the USB
> interrupt endpoint, the USB host controller driver needs to split up the
> request into 2 accesses according to the endpoints wMaxPacketSize of 8 byte.
> When the first transfer is answered by the eGalax device with not less than
> the full 8 byte requested, the host controller has got no way of knowing
> whether the touch controller has got additional data queued and will issue
> the second transfer. If per example a liftoff event finishes at such a
> wMaxPacketSize boundary, the data will not be available to the usbtouch driver
> until a further event is triggered and transfered to the host. From user
> perspective the BTN_TOUCH release event in this case is stuck until the next
> touch down event.
> 
> Signed-off-by: Christian Engelmayer <christian.engelmayer@frequentis.com>
> ---
>  drivers/input/touchscreen/usbtouchscreen.c |   16 ++++++++++++----
>  1 files changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/usbtouchscreen.c b/drivers/input/touchscreen/usbtouchscreen.c
> index 721fdb3..aa1f6a7 100644
> --- a/drivers/input/touchscreen/usbtouchscreen.c
> +++ b/drivers/input/touchscreen/usbtouchscreen.c
> @@ -76,6 +76,7 @@ struct usbtouch_device_info {
>  	int min_yc, max_yc;
>  	int min_press, max_press;
>  	int rept_size;
> +	int xmit_size;
>  
>  	/*
>  	 * Always service the USB devices irq not just when the input device is
> @@ -1523,7 +1524,7 @@ static int usbtouch_reset_resume(struct usb_interface *intf)
>  static void usbtouch_free_buffers(struct usb_device *udev,
>  				  struct usbtouch_usb *usbtouch)
>  {
> -	usb_free_coherent(udev, usbtouch->type->rept_size,
> +	usb_free_coherent(udev, usbtouch->type->xmit_size,
>  			  usbtouch->data, usbtouch->data_dma);
>  	kfree(usbtouch->buffer);
>  }
> @@ -1567,8 +1568,15 @@ static int usbtouch_probe(struct usb_interface *intf,
>  	usbtouch->type = type;
>  	if (!type->process_pkt)
>  		type->process_pkt = usbtouch_process_pkt;
> +	if (!type->xmit_size) {
> +		if ((type->get_pkt_len) &&
> +		    (type->rept_size > le16_to_cpu(endpoint->wMaxPacketSize)))
> +			type->xmit_size = le16_to_cpu(endpoint->wMaxPacketSize);
> +		else
> +			type->xmit_size = type->rept_size;

'type' points to a shared data structure and should not be modified. It
looks like we already violating this so a cleanup patch would be
appreciated as well.

BTW, maybe we should do:

	u16 wMaxPaxetSize = le16_to_cpu(endpoint->wMaxPacketSize);
	xmit_size = min(type->rept_size, wMaxPaxetSize);

?

Thanks.

-- 
Dmitry

  reply	other threads:[~2013-10-16  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 14:50 [PATCH] Input: usbtouchscreen - separate report and transmit buffer size handling Christian Engelmayer
2013-10-16  6:29 ` Dmitry Torokhov [this message]
     [not found]   ` <20131016062902.GA4282-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2013-10-16 21:15     ` [PATCH v2] " Christian Engelmayer

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=20131016062902.GA4282@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=christian.engelmayer@frequentis.com \
    --cc=daniel.ritz@gmx.ch \
    --cc=forest.bond@rapidrollout.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.