From: Chen-Yu Tsai <wens@csie.org>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Maxime Ripard <mripard@kernel.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [linux-sunxi] [PATCH 1/3] ARM: dts: sun8i: v3s: add EHCI/OHCI0 device nodes
Date: Mon, 23 Nov 2020 11:38:25 +0800 [thread overview]
Message-ID: <CAGb2v64BLcoYAd2VvP-bak3keqXfDpg1BoNaO8TZXiHxHOhP4Q@mail.gmail.com> (raw)
In-Reply-To: <20201122003841.1957034-2-icenowy@aosc.io>
On Sun, Nov 22, 2020 at 8:39 AM Icenowy Zheng <icenowy@aosc.io> wrote:
>
> The USB PHY 0 on V3s SoC can also be routed to a pair of EHCI/OHCI
> controllers.
>
> Add the device nodes for the controllers.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Chen-Yu Tsai <wens@csie.org>
WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens@csie.org>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: devicetree <devicetree@vger.kernel.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Maxime Ripard <mripard@kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-sunxi] [PATCH 1/3] ARM: dts: sun8i: v3s: add EHCI/OHCI0 device nodes
Date: Mon, 23 Nov 2020 11:38:25 +0800 [thread overview]
Message-ID: <CAGb2v64BLcoYAd2VvP-bak3keqXfDpg1BoNaO8TZXiHxHOhP4Q@mail.gmail.com> (raw)
In-Reply-To: <20201122003841.1957034-2-icenowy@aosc.io>
On Sun, Nov 22, 2020 at 8:39 AM Icenowy Zheng <icenowy@aosc.io> wrote:
>
> The USB PHY 0 on V3s SoC can also be routed to a pair of EHCI/OHCI
> controllers.
>
> Add the device nodes for the controllers.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Chen-Yu Tsai <wens@csie.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-23 3:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 0:38 [PATCH 0/3] ARM: dts: sun8i: v3s: enable EHCI/OHCI Icenowy Zheng
2020-11-22 0:38 ` Icenowy Zheng
2020-11-22 0:38 ` [PATCH 1/3] ARM: dts: sun8i: v3s: add EHCI/OHCI0 device nodes Icenowy Zheng
2020-11-22 0:38 ` Icenowy Zheng
2020-11-23 3:38 ` Chen-Yu Tsai [this message]
2020-11-23 3:38 ` [linux-sunxi] " Chen-Yu Tsai
2020-11-22 0:40 ` [PATCH 2/3] ARM: dts: sun8i: v3s: enable EHCI/OHCI for Lichee Pi Zero Icenowy Zheng
2020-11-22 0:40 ` Icenowy Zheng
2020-11-23 3:37 ` [linux-sunxi] " Chen-Yu Tsai
2020-11-23 3:37 ` Chen-Yu Tsai
2020-11-23 10:21 ` Icenowy Zheng
2020-11-23 10:21 ` Icenowy Zheng
2020-11-28 3:09 ` Chen-Yu Tsai
2020-11-28 3:09 ` Chen-Yu Tsai
2020-11-28 3:35 ` Icenowy Zheng
2020-11-28 3:35 ` Icenowy Zheng
2020-11-22 0:40 ` [PATCH 3/3] ARM: dts: sun8i: s3: switch PineCube to use OHCI/EHCI only Icenowy Zheng
2020-11-22 0:40 ` Icenowy Zheng
2020-11-23 3:29 ` [linux-sunxi] " Chen-Yu Tsai
2020-11-23 3:29 ` Chen-Yu Tsai
2020-11-23 11:43 ` Maxime Ripard
2020-11-23 11:43 ` Maxime Ripard
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=CAGb2v64BLcoYAd2VvP-bak3keqXfDpg1BoNaO8TZXiHxHOhP4Q@mail.gmail.com \
--to=wens@csie.org \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mripard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.