From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH] usb: dwc3: drd: Avoid error when extcon is missing
Date: Fri, 11 Dec 2020 16:49:36 +0200 [thread overview]
Message-ID: <20201211144936.GT4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201211142421.15389-1-semen.protsenko@linaro.org>
On Fri, Dec 11, 2020 at 04:24:21PM +0200, Sam Protsenko wrote:
> If "port" node is missing in PHY controller node, dwc3_get_extcon()
> isn't able to find extcon device. This is perfectly fine in case when
> "usb-role-switch" or OTG is used, but next misleading error message is
> printed in that case, from of_graph_get_remote_node():
>
> OF: graph: no port node found in /phy@1234abcd
>
> Avoid printing that message by checking if port node exists in PHY node
> before calling of_graph_get_remote_node().
So, this has to be v2...
Anyway, see below.
...
> static struct extcon_dev *dwc3_get_extcon(struct dwc3 *dwc)
> {
> struct device *dev = dwc->dev;
> - struct device_node *np_phy, *np_conn;
> - struct extcon_dev *edev;
> + struct device_node *np_phy;
> + struct extcon_dev *edev = NULL;
> const char *name;
>
> if (device_property_read_bool(dev, "extcon"))
> @@ -462,15 +462,22 @@ static struct extcon_dev *dwc3_get_extcon(struct dwc3 *dwc)
> return edev;
> }
>
> + /*
> + * Try to get extcon device from USB PHY controller's "port" node.
> + * Check if it has the "port" node first, to avoid printing the error
> + * message from underlying code, as it's a valid case: extcon device
> + * (and "port" node) may be missing in case of "usb-role-switch" or OTG
> + * mode.
> + */
> np_phy = of_parse_phandle(dev->of_node, "phys", 0);
> - np_conn = of_graph_get_remote_node(np_phy, -1, -1);
> + if (of_graph_is_present(np_phy)) {
> + struct device_node *np_conn;
>
> - if (np_conn)
> - edev = extcon_find_edev_by_node(np_conn);
> - else
> - edev = NULL;
> -
> - of_node_put(np_conn);
> + np_conn = of_graph_get_remote_node(np_phy, -1, -1);
> + if (np_conn)
> + edev = extcon_find_edev_by_node(np_conn);
> + of_node_put(np_conn);
> + }
> of_node_put(np_phy);
>
> return edev;
Why not do it slightly different, i.e.
- np_conn = of_graph_get_remote_node(np_phy, -1, -1);
+ if (of_graph_is_present(np_phy))
+ np_conn = of_graph_get_remote_node(np_phy, -1, -1);
+ else
+ np_conn = NULL;
?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-12-11 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 14:24 [PATCH] usb: dwc3: drd: Avoid error when extcon is missing Sam Protsenko
2020-12-11 14:49 ` Andy Shevchenko [this message]
2020-12-11 21:14 ` Sam Protsenko
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=20201211144936.GT4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=semen.protsenko@linaro.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;
as well as URLs for NNTP newsgroup(s).