mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: [PATCH 07/12] xhci: Add option to get next extended capability in list by passing id = 0
Date: Fri, 16 Feb 2018 11:43:16 +0100	[thread overview]
Message-ID: <20180216104321.8259-8-hdegoede@redhat.com> (raw)
In-Reply-To: <20180216104321.8259-1-hdegoede@redhat.com>

From: Mathias Nyman <mathias.nyman@linux.intel.com>

Modify xhci_find_next_ext_cap(base, offset, id) to return the next
capability offset if 0 is passed for id. Otherwise it will behave as
previously and return the offset of the next capability with matching id

capability id 0 is not used by xhci (reserved)

This is useful when we want to loop through all capabilities.

Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
 drivers/usb/host/xhci-ext-caps.h | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/usb/host/xhci-ext-caps.h b/drivers/usb/host/xhci-ext-caps.h
index bf7316e130d3..631e7cc62604 100644
--- a/drivers/usb/host/xhci-ext-caps.h
+++ b/drivers/usb/host/xhci-ext-caps.h
@@ -84,7 +84,8 @@
  * @base	PCI MMIO registers base address.
  * @start	address at which to start looking, (0 or HCC_PARAMS to start at
  *		beginning of list)
- * @id		Extended capability ID to search for.
+ * @id		Extended capability ID to search for, or 0 for the next
+ *		capability
  *
  * Returns the offset of the next matching extended capability structure.
  * Some capabilities can occur several times, e.g., the XHCI_EXT_CAPS_PROTOCOL,
@@ -110,7 +111,7 @@ static inline int xhci_find_next_ext_cap(void __iomem *base, u32 start, int id)
 		val = readl(base + offset);
 		if (val == ~0)
 			return 0;
-		if (XHCI_EXT_CAPS_ID(val) == id && offset != start)
+		if (offset != start && (id == 0 || XHCI_EXT_CAPS_ID(val) == id))
 			return offset;
 
 		next = XHCI_EXT_CAPS_NEXT(val);
-- 
2.14.3

  parent reply	other threads:[~2018-02-16 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 10:43 [PATCH 0/12] USB Type-C device-connection, mux and switch support Hans de Goede
2018-02-16 10:43 ` [PATCH 01/12] drivers: base: Unified device connection lookup Hans de Goede
2018-02-16 10:43 ` [PATCH 02/12] usb: typec: Start using ERR_PTR Hans de Goede
2018-02-16 10:43 ` [PATCH 03/12] usb: typec: API for controlling USB Type-C Multiplexers Hans de Goede
2018-02-16 10:43 ` [PATCH 04/12] usb: common: Small class for USB role switches Hans de Goede
2018-02-16 10:43 ` [PATCH 05/12] usb: typec: tcpm: Set USB role switch to device mode when configured as such Hans de Goede
2018-02-16 10:43 ` [PATCH 06/12] usb: typec: tcpm: Use new Type-C switch/mux and usb-role-switch functions Hans de Goede
2018-02-16 10:43 ` Hans de Goede [this message]
2018-02-16 10:43 ` [PATCH 08/12] xhci: Add Intel extended cap / otg phy mux handling Hans de Goede
2018-02-16 10:43 ` [PATCH 09/12] usb: roles: Add Intel XHCI USB role switch driver Hans de Goede
2018-02-16 10:43 ` [PATCH 10/12] usb: typec: driver for Pericom PI3USB30532 Type-C cross switch Hans de Goede
2018-02-16 10:43 ` [PATCH 11/12] platform/x86: intel_cht_int33fe: Add device connections for the Type-C port Hans de Goede
2018-02-16 10:43 ` [PATCH 12/12] extcon: axp288: Set USB role where necessary Hans de Goede
2018-02-16 10:44 ` [PATCH 0/12] USB Type-C device-connection, mux and switch support Hans de Goede
2018-02-16 10:47 [PATCH 00/12] " Hans de Goede
2018-02-16 10:47 ` [PATCH 07/12] xhci: Add option to get next extended capability in list by passing id = 0 Hans de Goede
2018-02-16 13:21   ` Heikki Krogerus

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=20180216104321.8259-8-hdegoede@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=tj@kernel.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 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®