From: Felipe Balbi <balbi@kernel.org>
To: Anurag Kumar Vulisha <anuragku@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Johan Hovold <johan@kernel.org>,
Jaejoong Kim <climbbb.kim@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Roger Quadros <rogerq@ti.com>,
Manu Gautam <mgautam@codeaurora.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
Bart Van Assche <bvanassche@acm.org>,
Mike Christie <mchristi@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Colin Ian King <colin.king@canonical.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"v.anuragkumar@gmail.com" <v.anuragkumar@gmail.com>,
Thinh Nguyen <thinhn@synopsys.com>,
Tejas Joglekar <tejas.joglekar@synopsys.com>,
Ajay Yugalkishore Pandey <APANDEY@xilinx.com>
Subject: [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields
Date: Mon, 10 Dec 2018 08:54:13 +0200 [thread overview]
Message-ID: <87pnu927oq.fsf@linux.intel.com> (raw)
Hi,
Anurag Kumar Vulisha <anuragku@xilinx.com> writes:
> HI Felipe,
>
>>-----Original Message-----
>>From: Felipe Balbi [mailto:balbi@kernel.org]
>>Sent: Friday, December 07, 2018 11:42 AM
>>To: Anurag Kumar Vulisha <anuragku@xilinx.com>; Greg Kroah-Hartman
>><gregkh@linuxfoundation.org>; Shuah Khan <shuah@kernel.org>; Alan Stern
>><stern@rowland.harvard.edu>; Johan Hovold <johan@kernel.org>; Jaejoong Kim
>><climbbb.kim@gmail.com>; Benjamin Herrenschmidt <benh@kernel.crashing.org>;
>>Roger Quadros <rogerq@ti.com>; Manu Gautam <mgautam@codeaurora.org>;
>>martin.petersen@oracle.com; Bart Van Assche <bvanassche@acm.org>; Mike
>>Christie <mchristi@redhat.com>; Matthew Wilcox <willy@infradead.org>; Colin Ian
>>King <colin.king@canonical.com>
>>Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org;
>>v.anuragkumar@gmail.com; Thinh Nguyen <thinhn@synopsys.com>; Tejas Joglekar
>><tejas.joglekar@synopsys.com>; Ajay Yugalkishore Pandey <APANDEY@xilinx.com>
>>Subject: RE: [PATCH v7 09/10] usb: dwc3: Check for IOC/LST bit in both event->status
>>and TRB->ctrl fields
>>
>>
>>Hi,
>>
>>Anurag Kumar Vulisha <anuragku@xilinx.com> writes:
>>>>> @@ -2286,7 +2286,12 @@ static int
>>>>dwc3_gadget_ep_reclaim_completed_trb(struct dwc3_ep *dep,
>>>>> if (event->status & DEPEVT_STATUS_SHORT && !chain)
>>>>> return 1;
>>>>>
>>>>> - if (event->status & (DEPEVT_STATUS_IOC | DEPEVT_STATUS_LST))
>>>>> + if ((event->status & DEPEVT_STATUS_IOC) &&
>>>>> + (trb->ctrl & DWC3_TRB_CTRL_IOC))
>>>>> + return 1;
>>>>
>>>>this shouldn't be necessary. According to databook, event->status
>>>>contains the bits from the completed TRB. Which means that
>>>>event->status & IOC will always be equal to trb->ctrl & IOC.
>>>>
>>> Thanks for reviewing this patch. Lets consider an example where a
>>> request has num_sgs > 0 and each sg is mapped to a TRB and the last
>>> TRB has the IOC bit set. Once the controller is done with the
>>> transfer, it generates XferInProgress for the last TRB (since IOC bit
>>> is set). As a part of trb reclaim process
>>> dwc3_gadget_ep_reclaim_trb_sg() calls
>>> dwc3_gadget_ep_reclaim_completed_trb() for req->num_sgs times. Since
>>> the event already has the IOC bit set, the loop is exited from the
>>> loop at the very first TRB and the remaining TRBs (mapped to the sglist) are left
>>unhandled.
>>> To avoid this we modified the code to exit only if both TRB & event
>>> has the IOC bit set.
>>
>>Seems like IOC case should just test for chain flag as well:
>>
>
> Okay. Along with this logic the code for updating chain bit should also be modified I guess.
not really
> Since the IOC bit is also set when there are not enough TRBs available, the code should be
> modified to not set DWC3_TRB_CTRL_CHN bit when the IOC bit is set. I will update below
> changes along with your suggestions and resend the patches.
no. Actually I don't think we're allowed to split a scatter/gather like
that. I did that quite a while ago, but I don't think we're allowed to
do so. What we should do, in that case, is not even queue that request
until we have enough for all members of the scatter/gather. But that's a
separate patch, anyway.
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@kernel.org>
To: Anurag Kumar Vulisha <anuragku@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Johan Hovold <johan@kernel.org>,
Jaejoong Kim <climbbb.kim@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Roger Quadros <rogerq@ti.com>,
Manu Gautam <mgautam@codeaurora.org>,
"martin.petersen\@oracle.com" <martin.petersen@oracle.com>,
Bart Van Assche <bvanassche@acm.org>,
Mike Christie <mchristi@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Colin Ian King <colin.king@canonical.com>
Cc: "linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"v.anuragkumar\@gmail.com" <v.anuragkumar@gmail.com>,
Thinh Nguyen <thinhn@synopsys.com>,
Tejas Joglekar <tejas.joglekar@synopsys.com>,
Ajay Yugalkishore Pandey <APANDEY@xilinx.com>
Subject: RE: [PATCH v7 09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields
Date: Mon, 10 Dec 2018 08:54:13 +0200 [thread overview]
Message-ID: <87pnu927oq.fsf@linux.intel.com> (raw)
In-Reply-To: <BL0PR02MB56331B2ECFFEB96A99936C32A7AB0@BL0PR02MB5633.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3256 bytes --]
Hi,
Anurag Kumar Vulisha <anuragku@xilinx.com> writes:
> HI Felipe,
>
>>-----Original Message-----
>>From: Felipe Balbi [mailto:balbi@kernel.org]
>>Sent: Friday, December 07, 2018 11:42 AM
>>To: Anurag Kumar Vulisha <anuragku@xilinx.com>; Greg Kroah-Hartman
>><gregkh@linuxfoundation.org>; Shuah Khan <shuah@kernel.org>; Alan Stern
>><stern@rowland.harvard.edu>; Johan Hovold <johan@kernel.org>; Jaejoong Kim
>><climbbb.kim@gmail.com>; Benjamin Herrenschmidt <benh@kernel.crashing.org>;
>>Roger Quadros <rogerq@ti.com>; Manu Gautam <mgautam@codeaurora.org>;
>>martin.petersen@oracle.com; Bart Van Assche <bvanassche@acm.org>; Mike
>>Christie <mchristi@redhat.com>; Matthew Wilcox <willy@infradead.org>; Colin Ian
>>King <colin.king@canonical.com>
>>Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org;
>>v.anuragkumar@gmail.com; Thinh Nguyen <thinhn@synopsys.com>; Tejas Joglekar
>><tejas.joglekar@synopsys.com>; Ajay Yugalkishore Pandey <APANDEY@xilinx.com>
>>Subject: RE: [PATCH v7 09/10] usb: dwc3: Check for IOC/LST bit in both event->status
>>and TRB->ctrl fields
>>
>>
>>Hi,
>>
>>Anurag Kumar Vulisha <anuragku@xilinx.com> writes:
>>>>> @@ -2286,7 +2286,12 @@ static int
>>>>dwc3_gadget_ep_reclaim_completed_trb(struct dwc3_ep *dep,
>>>>> if (event->status & DEPEVT_STATUS_SHORT && !chain)
>>>>> return 1;
>>>>>
>>>>> - if (event->status & (DEPEVT_STATUS_IOC | DEPEVT_STATUS_LST))
>>>>> + if ((event->status & DEPEVT_STATUS_IOC) &&
>>>>> + (trb->ctrl & DWC3_TRB_CTRL_IOC))
>>>>> + return 1;
>>>>
>>>>this shouldn't be necessary. According to databook, event->status
>>>>contains the bits from the completed TRB. Which means that
>>>>event->status & IOC will always be equal to trb->ctrl & IOC.
>>>>
>>> Thanks for reviewing this patch. Lets consider an example where a
>>> request has num_sgs > 0 and each sg is mapped to a TRB and the last
>>> TRB has the IOC bit set. Once the controller is done with the
>>> transfer, it generates XferInProgress for the last TRB (since IOC bit
>>> is set). As a part of trb reclaim process
>>> dwc3_gadget_ep_reclaim_trb_sg() calls
>>> dwc3_gadget_ep_reclaim_completed_trb() for req->num_sgs times. Since
>>> the event already has the IOC bit set, the loop is exited from the
>>> loop at the very first TRB and the remaining TRBs (mapped to the sglist) are left
>>unhandled.
>>> To avoid this we modified the code to exit only if both TRB & event
>>> has the IOC bit set.
>>
>>Seems like IOC case should just test for chain flag as well:
>>
>
> Okay. Along with this logic the code for updating chain bit should also be modified I guess.
not really
> Since the IOC bit is also set when there are not enough TRBs available, the code should be
> modified to not set DWC3_TRB_CTRL_CHN bit when the IOC bit is set. I will update below
> changes along with your suggestions and resend the patches.
no. Actually I don't think we're allowed to split a scatter/gather like
that. I did that quite a while ago, but I don't think we're allowed to
do so. What we should do, in that case, is not even queue that request
until we have enough for all members of the scatter/gather. But that's a
separate patch, anyway.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-12-10 6:54 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 6:54 Felipe Balbi [this message]
2018-12-10 6:54 ` [PATCH v7 09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2019-01-04 14:17 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Anurag Kumar Vulisha
2019-01-04 14:17 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-12 15:11 [v7,01/10] " Anurag Kumar Vulisha
2018-12-12 15:11 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-10 9:03 [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Felipe Balbi
2018-12-10 9:03 ` [PATCH v7 09/10] " Felipe Balbi
2018-12-10 8:56 [v7,09/10] " Anurag Kumar Vulisha
2018-12-10 8:56 ` [PATCH v7 09/10] " Anurag Kumar Vulisha
2018-12-08 19:03 [v7,09/10] " Anurag Kumar Vulisha
2018-12-08 19:03 ` [PATCH v7 09/10] " Anurag Kumar Vulisha
2018-12-07 17:09 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Alan Stern
2018-12-07 17:09 ` [PATCH v7 01/10] " Alan Stern
2018-12-07 6:11 [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Felipe Balbi
2018-12-07 6:11 ` [PATCH v7 09/10] " Felipe Balbi
2018-12-07 6:05 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Felipe Balbi
2018-12-07 6:05 ` [PATCH v7 01/10] " Felipe Balbi
2018-12-05 19:05 [v7,05/10] usb: dwc3: make controller clear transfer resources after complete Anurag Kumar Vulisha
2018-12-05 19:05 ` [PATCH v7 05/10] " Anurag Kumar Vulisha
2018-12-05 19:01 [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Anurag Kumar Vulisha
2018-12-05 19:01 ` [PATCH v7 09/10] " Anurag Kumar Vulisha
2018-12-05 15:43 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Anurag Kumar Vulisha
2018-12-05 15:43 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-05 9:07 [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Felipe Balbi
2018-12-05 9:07 ` [PATCH v7 09/10] " Felipe Balbi
2018-12-05 9:01 [v7,05/10] usb: dwc3: make controller clear transfer resources after complete Felipe Balbi
2018-12-05 9:01 ` [PATCH v7 05/10] " Felipe Balbi
2018-12-04 19:28 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Alan Stern
2018-12-04 19:28 ` [PATCH v7 01/10] " Alan Stern
2018-12-04 19:07 [v7,01/10] " Anurag Kumar Vulisha
2018-12-04 19:07 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-04 16:46 [v7,01/10] " Alan Stern
2018-12-04 16:46 ` [PATCH v7 01/10] " Alan Stern
2018-12-04 16:18 [v7,01/10] " Anurag Kumar Vulisha
2018-12-04 16:18 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-03 23:08 [v7,01/10] " Alan Stern
2018-12-03 23:08 ` [PATCH v7 01/10] " Alan Stern
2018-12-03 16:05 [v7,01/10] " Anurag Kumar Vulisha
2018-12-03 16:05 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-03 14:51 [v7,01/10] " Alan Stern
2018-12-03 14:51 ` [PATCH v7 01/10] " Alan Stern
2018-12-03 10:23 [v7,01/10] " Anurag Kumar Vulisha
2018-12-03 10:23 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-02 16:36 [v7,01/10] " Alan Stern
2018-12-02 16:36 ` [PATCH v7 01/10] " Alan Stern
2018-12-01 11:13 [v7,10/10] usb: dwc3: Check MISSED ISOC bit only for ISOC endpoints Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 10/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,09/10] usb: dwc3: Check for IOC/LST bit in both event->status and TRB->ctrl fields Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 09/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,08/10] usb: dwc3: Correct the logic for checking TRB full in __dwc3_prepare_one_trb() Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 08/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,07/10] usb: dwc3: check for requests in started list for stream capable endpoints Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 07/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,06/10] usb: dwc3: don't issue no-op trb " Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 06/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,05/10] usb: dwc3: make controller clear transfer resources after complete Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 05/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,04/10] usb: dwc3: update stream id in depcmd Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 04/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,03/10] usb: dwc3: gadget: handle stream events Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 03/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,02/10] usb: gadget: function: tcm: Add timeout for stream capable endpoints Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 02/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [v7,01/10] usb: gadget: udc: Add timer support for usb requests Anurag Kumar Vulisha
2018-12-01 11:13 ` [PATCH v7 01/10] " Anurag Kumar Vulisha
2018-12-01 11:13 [PATCH v7 00/10] usb: dwc3: Fix broken BULK stream support to dwc3 gadget driver Anurag Kumar Vulisha
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=87pnu927oq.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=APANDEY@xilinx.com \
--cc=anuragku@xilinx.com \
--cc=benh@kernel.crashing.org \
--cc=bvanassche@acm.org \
--cc=climbbb.kim@gmail.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchristi@redhat.com \
--cc=mgautam@codeaurora.org \
--cc=rogerq@ti.com \
--cc=shuah@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tejas.joglekar@synopsys.com \
--cc=thinhn@synopsys.com \
--cc=v.anuragkumar@gmail.com \
--cc=willy@infradead.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.