From: Matthias Kaehlcke <mka@chromium.org>
To: Javier Carrasco <javier.carrasco@wolfvision.net>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Matthias Kaehlcke <matthias@kaehlcke.net>
Subject: Re: [PATCH v3 1/7] usb: misc: onboard_hub: rename to onboard_dev
Date: Wed, 21 Feb 2024 18:22:44 +0000 [thread overview]
Message-ID: <ZdY_dBZyqiys0gf_@google.com> (raw)
In-Reply-To: <36b813ad-fdcb-495b-9d27-3573b6177831@wolfvision.net>
On Tue, Feb 13, 2024 at 11:36:25AM +0100, Javier Carrasco wrote:
> Hi Matthias,
>
> On 06.02.24 18:55, Matthias Kaehlcke wrote:
> > Hi Javier,
> >
> > a few comments inline
> >
> > On Tue, Feb 06, 2024 at 02:59:29PM +0100, Javier Carrasco wrote:
> >> +static struct onboard_dev *_find_onboard_dev(struct device *dev)
> >> +{
> >> + struct platform_device *pdev;
> >> + struct device_node *np;
> >> + struct onboard_dev *onboard_dev;
> >> +
> >> + pdev = of_find_device_by_node(dev->of_node);
> >> + if (!pdev) {
> >> + np = of_parse_phandle(dev->of_node, "peer-hub", 0);
> >> + if (!np) {
> >> + dev_err(dev, "failed to find device node for peer hub\n");
> >> + return ERR_PTR(-EINVAL);
> >> + }
> >> +
> >> + pdev = of_find_device_by_node(np);
> >> + of_node_put(np);
> >> +
> >> + if (!pdev)
> >> + return ERR_PTR(-ENODEV);
> >> + }
> >
> > The above branch should probably be guarded by 'if (!onboard_dev->pdata->is_hub)',
> > this is also a change for ""usb: misc: onboard_dev: add support for non-hub devices"
> >
> I am not sure how to guard the branch like that because onboard_dev is
> retrieved by means of pdev->dev, which is not available if
> of_find_device_by_node returns NULL. The non-hub device will not have a
> peer-hub property according to its bindings anyway, right?
Right, onboard_dev isn't available yet at that point, my bad. I thought it
would be nice to clearly separate the hub related logic from other devices,
but that isn't an option in this case.
next prev parent reply other threads:[~2024-02-21 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 13:59 [PATCH v3 0/7] usb: misc: onboard_hub: add support for XMOS XVF3500 Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 1/7] usb: misc: onboard_hub: rename to onboard_dev Javier Carrasco
2024-02-06 17:55 ` Matthias Kaehlcke
2024-02-13 10:36 ` Javier Carrasco
2024-02-21 18:22 ` Matthias Kaehlcke [this message]
2024-02-06 13:59 ` [PATCH v3 2/7] usb: misc: onboard_dev: add support for non-hub devices Javier Carrasco
2024-02-06 18:40 ` Matthias Kaehlcke
2024-02-13 10:00 ` Javier Carrasco
2024-02-21 18:33 ` Matthias Kaehlcke
2024-02-06 13:59 ` [PATCH v3 3/7] drm: ci: arm64.config: update ONBOARD_USB_HUB to ONBOARD_USB_DEV Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 4/7] arm64: defconfig: " Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 5/7] ARM: multi_v7_defconfig: update ONBOARD_USB_HUB name Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 6/7] ASoC: dt-bindings: xmos,xvf3500: add XMOS XVF3500 voice processor Javier Carrasco
2024-02-06 14:32 ` Mark Brown
2024-02-06 15:05 ` Javier Carrasco
2024-02-06 15:22 ` Matthias Kaehlcke
2024-02-06 15:35 ` Javier Carrasco
2024-02-06 16:22 ` Mark Brown
2024-02-06 15:35 ` Mark Brown
2024-02-06 15:38 ` Javier Carrasco
2024-02-06 15:49 ` Matthias Kaehlcke
2024-02-06 16:35 ` Mark Brown
2024-02-06 13:59 ` [PATCH v3 7/7] usb: misc: onboard_hub: add support for XMOS XVF3500 Javier Carrasco
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=ZdY_dBZyqiys0gf_@google.com \
--to=mka@chromium.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=javier.carrasco@wolfvision.net \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias@kaehlcke.net \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).