From: Alan Stern <stern@rowland.harvard.edu>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Mathias Nyman" <mathias.nyman@linux.intel.com>,
"Michał Pecio" <michal.pecio@gmail.com>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
gregkh@linuxfoundation.org, laurent.pinchart@ideasonboard.com,
hdegoede@redhat.com, Thinh.Nguyen@synopsys.com,
"Amardeep Rai" <amardeep.rai@intel.com>,
"Kannappan R" <r.kannappan@intel.com>
Subject: Re: [PATCH v4 3/4] USB: Add a function to obtain USB version independent maximum bpi value
Date: Mon, 18 Aug 2025 09:39:48 -0400 [thread overview]
Message-ID: <f8e186a9-015f-4df3-bc10-33eeef1146dd@rowland.harvard.edu> (raw)
In-Reply-To: <aKMY0XPLmK-TOWIt@kekkonen.localdomain>
On Mon, Aug 18, 2025 at 12:13:05PM +0000, Sakari Ailus wrote:
> > > how about one of these:
> > > usb_endpoint_max_periodic_bytes()
> > > usb_endpoint_max_periodic_payload()
> > > usb_endpoint_max_periodic_bpi()
> >
> > How about usb_endpoint_max_si_payload() ("si" being for service interval)?
>
> I somehow missed your latter sentence earlier. I'm totally fine with these,
> perhaps I'm slightly leaning towards usb_endpoint_max_periodic_payload()
> but let's see what others think.
I'm okay with either usb_endpoint_max_periodic_bytes() or
usb_endpoint_max_periodic_payload().
Alan Stern
next prev parent reply other threads:[~2025-08-18 13:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 13:24 [PATCH v4 0/4] eUSB2 Double Isochronous IN Bandwidth support Sakari Ailus
2025-08-12 13:24 ` [PATCH v4 1/4] xhci: Add host support for eUSB2 double isochronous bandwidth devices Sakari Ailus
2025-08-18 9:50 ` Michał Pecio
2025-08-18 15:30 ` Mathias Nyman
2025-08-19 14:01 ` Sakari Ailus
2025-08-20 8:24 ` Sakari Ailus
2025-08-20 8:43 ` Michał Pecio
2025-08-20 13:19 ` Sakari Ailus
2025-08-12 13:24 ` [PATCH v4 2/4] USB: core: support eUSB2 double bandwidth large isoc URB frames Sakari Ailus
2025-08-12 13:24 ` [PATCH v4 3/4] USB: Add a function to obtain USB version independent maximum bpi value Sakari Ailus
2025-08-12 13:58 ` Alan Stern
2025-08-13 14:49 ` Michał Pecio
2025-08-18 6:08 ` Sakari Ailus
2025-08-18 7:32 ` Mathias Nyman
2025-08-18 8:37 ` Michał Pecio
2025-08-18 11:27 ` Sakari Ailus
2025-08-18 12:13 ` Sakari Ailus
2025-08-18 13:39 ` Alan Stern [this message]
2025-08-12 13:24 ` [PATCH v4 4/4] media: uvcvideo: eUSB2 double isochronous bandwidth support Sakari Ailus
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=f8e186a9-015f-4df3-bc10-33eeef1146dd@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=Thinh.Nguyen@synopsys.com \
--cc=amardeep.rai@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@gmail.com \
--cc=r.kannappan@intel.com \
--cc=sakari.ailus@linux.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).