From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-usb@vger.kernel.org,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org,
Casey G Bowman <casey.g.bowman@intel.com>,
Rajmohan Mani <rajmohan.mani@intel.com>,
Christian Kellner <ckellner@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 2/9] thunderbolt: Add USB4 port devices
Date: Wed, 19 May 2021 18:14:47 +0300 [thread overview]
Message-ID: <YKUrZ0b4UObhtV9k@kuha.fi.intel.com> (raw)
In-Reply-To: <20210519141259.84839-3-mika.westerberg@linux.intel.com>
On Wed, May 19, 2021 at 05:12:52PM +0300, Mika Westerberg wrote:
> Create devices for each USB4 port. This is needed when we add retimer
> access when there is no device connected but may be useful for other
> purposes too following what USB subsystem does. This exports a single
> attribute "link" that shows the type of the USB4 link (or "none" if
> there is no cable connected).
<snip>
> +/*
> + * USB4 port device
> + *
> + * Copyright (C) 2021, Intel Corporation
> + * Author: Mika Westerberg <mika.westerberg@linux.intel.com>
> + */
> +
> +#include <linux/acpi.h>
> +#include <linux/pm_runtime.h>
> +
> +#include "tb.h"
> +
> +static ssize_t link_show(struct device *dev, struct device_attribute *attr,
> + char *buf)
> +{
> + struct usb4_port *usb4 = tb_to_usb4_port_device(dev);
> + struct tb_port *port = usb4->port;
> + struct tb *tb = port->sw->tb;
> + const char *link;
> +
> + if (mutex_lock_interruptible(&tb->lock))
> + return -ERESTARTSYS;
> +
> + if (tb_is_upstream_port(port))
> + link = port->sw->link_usb4 ? "usb4" : "tbt";
> + else if (tb_port_has_remote(port))
> + link = port->remote->sw->link_usb4 ? "usb4" : "tbt";
> + else
> + link = "none";
> +
> + mutex_unlock(&tb->lock);
> +
> + return sysfs_emit(buf, "%s\n", link);
> +}
> +static DEVICE_ATTR_RO(link);
> +
> +static struct attribute *common_attrs[] = {
> + &dev_attr_link.attr,
> + NULL
> +};
> +
> +static const struct attribute_group common_group = {
> + .attrs = common_attrs,
> +};
> +
> +static const struct attribute_group *usb4_port_device_groups[] = {
> + &common_group,
> + NULL
> +};
> +
> +static void usb4_port_device_release(struct device *dev)
> +{
> + struct usb4_port *usb4 = container_of(dev, struct usb4_port, dev);
> +
> + kfree(usb4);
> +}
> +
> +struct device_type usb4_port_device_type = {
> + .name = "usb4_port",
> + .groups = usb4_port_device_groups,
> + .release = usb4_port_device_release,
> +};
I noticed that in the next patch you add acpi_bus_type for these
ports, but is that really necessary? Why not just:
int usb4_port_fwnode_match(struct tb_port *port, struct fwnode_handle *fwnode)
{
if (is_acpi_device_node(fwnode))
return acpi_device_adr(to_acpi_device_node(fwnode)) == port->port;
return 0;
}
> +/**
> + * usb4_port_device_add() - Add USB4 port device
> + * @port: Lane 0 adapter port to add the USB4 port
> + *
> + * Creates and registers a USB4 port device for @port. Returns the new
> + * USB4 port device pointer or ERR_PTR() in case of error.
> + */
> +struct usb4_port *usb4_port_device_add(struct tb_port *port)
> +{
struct fwnode_handle *child;
> + struct usb4_port *usb4;
> + int ret;
> +
> + usb4 = kzalloc(sizeof(*usb4), GFP_KERNEL);
> + if (!usb4)
> + return ERR_PTR(-ENOMEM);
> +
> + usb4->port = port;
> + usb4->dev.type = &usb4_port_device_type;
> + usb4->dev.parent = &port->sw->dev;
> + dev_set_name(&usb4->dev, "usb4_port%d", port->port);
and then here something like this (feel free to improve this part):
device_for_each_child_node(&port->sw->dev, child) {
if (usb4_port_fwnode_match(port, child)) {
usb4->dev.fwnode = child;
break;
}
}
Or maybe I'm missing something?
> + ret = device_register(&usb4->dev);
> + if (ret) {
> + put_device(&usb4->dev);
> + return ERR_PTR(ret);
> + }
> +
> + pm_runtime_no_callbacks(&usb4->dev);
> + pm_runtime_set_active(&usb4->dev);
> + pm_runtime_enable(&usb4->dev);
> + pm_runtime_set_autosuspend_delay(&usb4->dev, TB_AUTOSUSPEND_DELAY);
> + pm_runtime_mark_last_busy(&usb4->dev);
> + pm_runtime_use_autosuspend(&usb4->dev);
> +
> + return usb4;
> +}
thanks,
--
heikki
next prev parent reply other threads:[~2021-05-19 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 14:12 [PATCH 0/9] thunderbolt: Offline on-board retimer NVM upgrade support Mika Westerberg
2021-05-19 14:12 ` [PATCH 1/9] thunderbolt: Log the link as TBT instead of TBT3 Mika Westerberg
2021-05-19 14:12 ` [PATCH 2/9] thunderbolt: Add USB4 port devices Mika Westerberg
2021-05-19 15:14 ` Heikki Krogerus [this message]
2021-05-19 15:30 ` Heikki Krogerus
2021-05-19 15:40 ` Mika Westerberg
2021-05-20 9:23 ` Heikki Krogerus
2021-05-19 14:12 ` [PATCH 3/9] thunderbolt: Add support for ACPI _DSM to power on/off retimers Mika Westerberg
2021-05-19 14:12 ` [PATCH 4/9] thunderbolt: Add additional USB4 port operations for retimer access Mika Westerberg
2021-05-19 14:12 ` [PATCH 5/9] thunderbolt: Add support for retimer NVM upgrade when there is no link Mika Westerberg
2021-05-19 14:12 ` [PATCH 6/9] thunderbolt: Move nvm_write_ops to tb.h Mika Westerberg
2021-05-19 14:12 ` [PATCH 7/9] thunderbolt: Allow router NVM authenticate separately Mika Westerberg
2021-05-19 14:12 ` [PATCH 8/9] thunderbolt: Add WRITE_ONLY and AUTHENTICATE_ONLY NVM operations for retimers Mika Westerberg
2021-05-19 14:12 ` [PATCH 9/9] thunderbolt: Check for NVM authentication status after the operation started Mika Westerberg
2021-05-20 8:59 ` [PATCH 0/9] thunderbolt: Offline on-board retimer NVM upgrade support Greg Kroah-Hartman
2021-06-01 7:56 ` Mika Westerberg
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=YKUrZ0b4UObhtV9k@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=casey.g.bowman@intel.com \
--cc=ckellner@redhat.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rajmohan.mani@intel.com \
--cc=rjw@rjwysocki.net \
/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