From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Pin-yen Lin <treapking@chromium.org>
Cc: "Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <robert.foss@linaro.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Daniel Scally" <djrscally@gmail.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Prashant Malani" <pmalani@chromium.org>,
"Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Stephen Boyd" <swboyd@chromium.org>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Marek Vasut" <marex@denx.de>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Lyude Paul" <lyude@redhat.com>,
chrome-platform@lists.linux.dev, "Xin Ji" <xji@analogixsemi.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org,
"Allen Chen" <allen.chen@ite.com.tw>,
linux-acpi@vger.kernel.org, "Hsin-Yi Wang" <hsinyi@chromium.org>,
"Chen-Yu Tsai" <wenst@chromium.org>
Subject: Re: [PATCH v10 1/9] device property: Add remote endpoint to devcon matcher
Date: Thu, 12 Jan 2023 13:32:34 +0000 [thread overview]
Message-ID: <Y8AL8nTcNcl6zX7H@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20230112042104.4107253-2-treapking@chromium.org>
Hi Pin-yen,
On Thu, Jan 12, 2023 at 12:20:56PM +0800, Pin-yen Lin wrote:
> From: Prashant Malani <pmalani@chromium.org>
>
> When searching the device graph for device matches, check the
> remote-endpoint itself for a match.
>
> Some drivers register devices for individual endpoints. This allows
> the matcher code to evaluate those for a match too, instead
> of only looking at the remote parent devices. This is required when a
> device supports two mode switches in its endpoints, so we can't simply
> register the mode switch with the parent node.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> Signed-off-by: Pin-yen Lin <treapking@chromium.org>
> Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
> Tested-by: Chen-Yu Tsai <wenst@chromium.org>
>
> ---
>
> Changes in v10:
> - Collected Reviewed-by and Tested-by tags
>
> Changes in v6:
> - New in v6
>
> drivers/base/property.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/base/property.c b/drivers/base/property.c
> index 2a5a37fcd998..48877af4e444 100644
> --- a/drivers/base/property.c
> +++ b/drivers/base/property.c
> @@ -1223,6 +1223,21 @@ static unsigned int fwnode_graph_devcon_matches(struct fwnode_handle *fwnode,
> break;
> }
>
> + /*
> + * Some drivers may register devices for endpoints. Check
> + * the remote-endpoints for matches in addition to the remote
> + * port parent.
> + */
> + node = fwnode_graph_get_remote_endpoint(ep);
> + if (fwnode_device_is_available(node)) {
> + ret = match(node, con_id, data);
> + if (ret) {
> + if (matches)
> + matches[count] = ret;
> + count++;
> + }
> + }
Aren't you missing fwnode_handle-put(node) here??
> +
> node = fwnode_graph_get_remote_port_parent(ep);
> if (!fwnode_device_is_available(node)) {
> fwnode_handle_put(node);
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2023-01-12 13:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 4:20 [PATCH v10 0/9] Register Type-C mode-switch in DP bridge endpoints Pin-yen Lin
2023-01-12 4:20 ` [PATCH v10 1/9] device property: Add remote endpoint to devcon matcher Pin-yen Lin
2023-01-12 13:27 ` Heikki Krogerus
2023-01-12 13:32 ` Sakari Ailus [this message]
2023-01-12 22:31 ` Prashant Malani
2023-01-13 17:40 ` Andy Shevchenko
2023-01-16 13:07 ` Sakari Ailus
2023-01-20 21:15 ` Prashant Malani
2023-01-12 4:20 ` [PATCH v10 2/9] platform/chrome: cros_ec_typec: Purge blocking switch devlinks Pin-yen Lin
2023-01-12 13:31 ` Heikki Krogerus
2023-01-12 4:20 ` [PATCH v10 3/9] drm/display: Add Type-C switch helpers Pin-yen Lin
2023-01-12 4:40 ` Dmitry Baryshkov
2023-01-12 5:19 ` Pin-yen Lin
2023-01-12 5:24 ` Dmitry Baryshkov
2023-01-12 5:48 ` Pin-yen Lin
2023-01-12 5:50 ` Dmitry Baryshkov
2023-01-12 8:17 ` Pin-yen Lin
2023-01-12 8:37 ` Jani Nikula
2023-01-13 8:19 ` Pin-yen Lin
2023-01-13 9:23 ` Heikki Krogerus
2023-01-13 16:57 ` Andy Shevchenko
2023-01-12 4:20 ` [PATCH v10 4/9] dt-bindings: display: bridge: anx7625: Add mode-switch support Pin-yen Lin
2023-01-12 4:43 ` Dmitry Baryshkov
2023-01-12 5:26 ` Pin-yen Lin
2023-01-12 5:27 ` Dmitry Baryshkov
2023-01-12 22:56 ` Rob Herring
2023-01-12 4:21 ` [PATCH v10 5/9] drm/bridge: anx7625: Check for Type-C during panel registration Pin-yen Lin
2023-01-12 4:21 ` [PATCH v10 6/9] drm/bridge: anx7625: Register Type C mode switches Pin-yen Lin
2023-01-12 4:21 ` [PATCH v10 7/9] dt-bindings: display: bridge: it6505: Add mode-switch support Pin-yen Lin
2023-01-12 4:21 ` [PATCH v10 8/9] drm/bridge: it6505: Fix Kconfig indentation Pin-yen Lin
2023-01-12 4:21 ` [PATCH v10 9/9] drm/bridge: it6505: Register Type C mode switches Pin-yen Lin
2023-01-12 12:32 ` Chen-Yu Tsai
2023-01-12 4:34 ` [PATCH v10 0/9] Register Type-C mode-switch in DP bridge endpoints Dmitry Baryshkov
2023-01-12 5:07 ` Pin-yen Lin
2023-01-12 10:36 ` Andy Shevchenko
2023-01-12 22:44 ` Rob Herring
2023-01-13 8:09 ` Pin-yen Lin
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=Y8AL8nTcNcl6zX7H@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hsinyi@chromium.org \
--cc=javierm@redhat.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=pmalani@chromium.org \
--cc=rafael@kernel.org \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=treapking@chromium.org \
--cc=tzimmermann@suse.de \
--cc=wenst@chromium.org \
--cc=xji@analogixsemi.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