All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Niklas Neronin <niklas.neronin@linux.intel.com>
Cc: linux-usb@vger.kernel.org, michal.pecio@gmail.com
Subject: Re: [PATCH v2 00/13] usb: xhci: Host Controller Capability Registers rework
Date: Wed, 19 Nov 2025 16:00:44 +0200	[thread overview]
Message-ID: <19b2f1a5-8426-485a-b99e-cfc21cf1e035@linux.intel.com> (raw)
In-Reply-To: <20251113125640.2875608-1-niklas.neronin@linux.intel.com>

On 11/13/25 14:56, Niklas Neronin wrote:
> This patch series focuses on improving the definitions and organization of
> the Host Controller Capability Registers macros in the xhci driver.
> It is the first step in a larger effort to clean up and restructure the
> xhci header files for better readability and maintainability.
> 
> Because the Structural Parameters 1 register (part of the HC Capability
> Registers) relies heavily on xhci-caps.h, a few related patches from
> another ongoing rework have been included here as well. These address the
> handling of Max Ports and Max Interrupters values.
> The Max Slots handling will follow the same pattern in a future series.
> That change is more involved and will be submitted separately.
> 
> v2 changes:
>   * Change xhci_ist_in_microseconds() argument to 'xhci'.
>   * Rename xhci_ist_in_microseconds() to xhci_ist_microframes().
>   * Revert to (1 << x) from BIT() operaion in HCC_MAX_PSA() macro.
>   * Added macro changes to DWC3 driver.

I'm taking this series up to and including PATCH 11/13.
I tink we can get this into 6.19

PATCH 12/13 touches dwc3, we can look at the rest for next kernel

Thanks
Mathias



      parent reply	other threads:[~2025-11-19 14:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 12:56 [PATCH v2 00/13] usb: xhci: Host Controller Capability Registers rework Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 01/13] usb: xhci: remove deprecated TODO comment Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 02/13] usb: xhci: remove unused trace operation and argument Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 03/13] usb: xhci: use cached HCSPARAMS1 value Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 04/13] usb: xhci: simplify handling of Structural Parameters 1 values Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 05/13] usb: xhci: limit number of ports to 127 Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 06/13] usb: xhci: limit number of interrupts to 128 Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 07/13] usb: xhci: improve xhci-caps.h comments Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 08/13] usb: xhci: simplify Isochronous Scheduling Threshold handling Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 09/13] usb: xhci: simplify Max Scratchpad buffer macros Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 10/13] usb: xhci: drop xhci-caps.h dependence on xhci-ext-caps.h Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 11/13] usb: xhci: standardize single bit-field macros Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 12/13] usb: xhci: standardize multi " Niklas Neronin
2025-11-13 12:56 ` [PATCH v2 13/13] usb: xhci: use 64-bit Addressing Capability macro Niklas Neronin
2025-11-19 14:00 ` Mathias Nyman [this message]

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=19b2f1a5-8426-485a-b99e-cfc21cf1e035@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michal.pecio@gmail.com \
    --cc=niklas.neronin@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 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.