Skip to content

device property: fwnode_is_compatible() helper

Heikki Krogerus linux-acpi linux-usb lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 4 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3device property: Add fwnode_is_compatible() and device_is_compatible() helpersdrivers/base/property.c include/linux/property.h+38 -01 reply
2/3usb: roles: Use the "compatible" property instead of a boolean propertydrivers/usb/roles/class.c+1 -10 replies
3/3usb: typec: mux: Use the "compatible" property instead of a boolean propertydrivers/usb/typec/mux.c+2 -61 reply

Reviews trailers per patch

None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchAndy Shevchenko
SeriesR-b
1/3
2/3
3/3

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/3] device property: fwnode_is_compatible() helper

Hi,

Basically the helper is just a generic version of the function of_device_is_compatible() that should work also with ACPI and software nodes.

As the first user for the helper, I'm converting in this series the USB role switch code to expect the "compatible" property to have the value "usb-role-switch" instead of expecting a boolean property named "usb-role-switch". I'm doing the same for the USB Type-C mux code.

thanks,

Heikki Krogerus (3):
device property: Add fwnode_is_compatible() and device_is_compatible()
helpers
usb: roles: Use the "compatible" property instead of a boolean
property
usb: typec: mux: Use the "compatible" property instead of a boolean
property

 drivers/base/property.c   | 35 +++++++++++++++++++++++++++++++++++
 drivers/usb/roles/class.c |  2 +-
 drivers/usb/typec/mux.c   |  8 ++------
 include/linux/property.h  |  3 +++
 4 files changed, 41 insertions(+), 7 deletions(-)
Signature · 1 line
2.20.1