mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Manan Aurora <maurora@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"manugautam@google.com" <manugautam@google.com>,
	"badhri@google.com" <badhri@google.com>
Subject: Re: [PATCH] usb: dwc3: Support EBC feature of DWC_usb31
Date: Fri, 17 Nov 2023 01:51:46 +0000	[thread overview]
Message-ID: <20231117015143.nzgqaes256lnz5ht@synopsys.com> (raw)
In-Reply-To: <CAJnM4-wew9b=Ge8QHLRiReNJAqgA0ngOW8WTVk4frta+y+9jYw@mail.gmail.com>

On Thu, Nov 16, 2023, Manan Aurora wrote:
> On Sat, Nov 11, 2023 at 4:39 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> >
> > On Thu, Nov 02, 2023, Manan Aurora wrote:
> > > Support configuration and use of bulk endpoints in the so-called EBC
> > > mode described in the DBC_usb31 databook (appendix E)
> > >
> > > Added a bit fifo_mode to usb_ep to indicate to the UDC driver that a
> > > specific endpoint is to operate in the EBC (or equivalent) mode when
> > > enabled
> >
> > This should be unique to dwc3, and it's only for bulk. I don't think
> > usb_ep or the user of usb_ep should know this.
> 
> In our use case we have a function driver that configures an allocated bulk
> endpoint to operate as an EBC EP. So the function driver already depends on the
> feature.

This should be abstracted from the function driver. The function driver
should not need to know about this feature.

> 
> dwc3_ep seems like the correct place to put this field but a function
> driver that allocates
> EPs and configures them for this use case would need to include dwc3 headers.
> If other vendors offer an equivalent feature this dependency would
> become an issue.
> 
> Exporting a symbol from dwc3 is an easy option but dwc3 doesn't
> currently export symbols
> hence I tried to avoid that
> 
> > Also since DWC3_DEPCFG_EBC_HWO_NOWB must be set, the controller does not
> > write back to the TRB. Did you handle how the driver would update the
> > usb request on completion? (e.g. how much was transferred).
> 
> In our use case, we intend to have a link TRB and issue a startXfer
> command. Completion
> handling and continuing the transfer will be offloaded to dedicated
> FIFO hardware.
> But we can definitely rework this to disable no-writeback mode by
> default and allow this to
> be separately enabled
> 

Ok.

Thanks,
Thinh

  reply	other threads:[~2023-11-17  1:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  7:38 Manan Aurora
2023-11-10 23:09 ` Thinh Nguyen
2023-11-16  5:19   ` Manan Aurora
2023-11-17  1:51     ` Thinh Nguyen [this message]
2024-01-17  1:11       ` Thinh Nguyen
2024-01-17  1:33         ` Manan Aurora
2024-01-17  1:59           ` Thinh Nguyen
2024-01-18  0:45             ` Thinh Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31  3:46 Manan Aurora

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=20231117015143.nzgqaes256lnz5ht@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=badhri@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=manugautam@google.com \
    --cc=maurora@google.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

all inboxes | Powered by JetHome®