public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Robert Baldyga <r.baldyga@samsung.com>
Cc: <balbi@ti.com>, <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<b.zolnierkie@samsung.com>, <m.szyprowski@samsung.com>,
	<andrzej.p@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2] USB: gadget: s3c-hsotg: add isochronous transfers support
Date: Tue, 1 Oct 2013 09:45:27 -0500	[thread overview]
Message-ID: <20131001144527.GX1476@radagast> (raw)
In-Reply-To: <1380016036-20983-1-git-send-email-r.baldyga@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]

Hi,

On Tue, Sep 24, 2013 at 11:47:16AM +0200, Robert Baldyga wrote:
> Hello,
> 
> This is update for my proposal for isochronous transfers support in s3c-hsotg
> driver. I've fixed issuses pointed by Bartlomiej Zolnierkiewicz. For more
> information, please check the change log at the end of the mail.

this shouldn't be part of commit log.

> This patch adds isochronous transfer support. It adds few modifications:
> - Modify s3c_hsotg_write_fifo() function. It actually calculates transfer
>   size, taking into account Multi Count value, which indicates number of
>   transactions per microframe.
> - Fix s3c_hsotg_start_req() function by setting number of packets to Multi
>   Count field in DIEPTSIZ register for isochronous endpoints.
> - Fix s3c_hsotg_set_ep_maxpacket() function. Field wMaxPacketSize of endpoint
>   descriptor is now splitted into maximum packet size value and number of
>   additional transaction per microframe.
> - Modify s3c_hsotg_epint() function. Some interrupts are ignored for
>   isochronous endpoints, (e.g. INTknTXFEmpMsk) becouse isochronous request is
>   always transfered in single transaction, which ends with XferCompl interrupt.
>   Add Odd/Even microframe toggle to allow data transfering in each microframe.
> - Fix s3c_hsotg_ep_enable() function by supporting isochronous endpoint type.

you're doing way too many things in a single patch.

> Signed-off-by: Robert Baldyga <r.baldyga@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> 
> Changelog:
> 
> v2:
> - moved bugfix affecting to the other features to separated patch
> - changed conditions order in request length checking in s3c_hsotg_start_req
>   function, as Bartlomiej Zolnierkiewicz suggested
> - fixed typos
> 
> v1: https://lkml.org/lkml/2013/9/23/72
> - initial proposal

changelog sould be after tearline (---) below.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-10-01 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  9:47 [PATCH v2] USB: gadget: s3c-hsotg: add isochronous transfers support Robert Baldyga
2013-10-01 14:45 ` Felipe Balbi [this message]
2013-10-02 10:34   ` Robert Baldyga
2013-10-04 14:36     ` Felipe Balbi

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=20131001144527.GX1476@radagast \
    --to=balbi@ti.com \
    --cc=andrzej.p@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=r.baldyga@samsung.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