From: "Måns Rullgård" <mans@mansr.com>
To: Bin Liu <b-liu@ti.com>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: musb: sunxi: propagate devicetree node to glue pdev
Date: Mon, 18 Mar 2019 14:29:00 +0000 [thread overview]
Message-ID: <yw1xwokw1ck3.fsf@mansr.com> (raw)
In-Reply-To: <20190228112031.8122-1-mans@mansr.com> (Mans Rullgard's message of "Thu, 28 Feb 2019 11:20:31 +0000")
Mans Rullgard <mans@mansr.com> writes:
> In order for devicetree nodes to be correctly associated with attached
> devices, the controller node needs to be propagated to the glue device.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>
> ---
> This depends on 2c1ea6abde88 ("platform: set of_node in
> platform_device_register_full()") which is currently winding its way
> through the staging trees.
That patch is now in next.
> ---
> drivers/usb/musb/sunxi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/musb/sunxi.c b/drivers/usb/musb/sunxi.c
> index 832a41f9ee7d..a72665fbf111 100644
> --- a/drivers/usb/musb/sunxi.c
> +++ b/drivers/usb/musb/sunxi.c
> @@ -781,6 +781,8 @@ static int sunxi_musb_probe(struct platform_device *pdev)
> pinfo.name = "musb-hdrc";
> pinfo.id = PLATFORM_DEVID_AUTO;
> pinfo.parent = &pdev->dev;
> + pinfo.fwnode = of_fwnode_handle(pdev->dev.of_node);
> + pinfo.of_node_reused = true;
> pinfo.res = pdev->resource;
> pinfo.num_res = pdev->num_resources;
> pinfo.data = &pdata;
> --
> 2.20.1
>
--
Måns Rullgård
next prev parent reply other threads:[~2019-03-18 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 11:20 [PATCH] usb: musb: sunxi: propagate devicetree node to glue pdev Mans Rullgard
2019-03-18 14:29 ` Måns Rullgård [this message]
2019-06-27 9:56 ` Måns Rullgård
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=yw1xwokw1ck3.fsf@mansr.com \
--to=mans@mansr.com \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.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).