From: Hans de Goede <hdegoede@redhat.com>
To: Icenowy Zheng <icenowy@aosc.xyz>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Reinder de Haan <patchesrdh@mveas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Tony Prisk <linux@prisktech.co.nz>, Chen-Yu Tsai <wens@csie.org>,
Rob Herring <robh+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH 3/3] ehci-platform: add the max clock number to 4
Date: Mon, 1 Aug 2016 09:27:12 +0200 [thread overview]
Message-ID: <01a348da-3b26-68a6-9d9f-c37d81b4fd64@redhat.com> (raw)
In-Reply-To: <414101470035152@web9j.yandex.ru>
Hi,
On 01-08-16 09:05, Icenowy Zheng wrote:
> clocks = <&ccu CLK_A64_BUS_OHCI1>,
> <&ccu CLK_A64_BUS_EHCI1>,
> <&ccu CLK_A64_USB_OHCI0>,
> <&ccu CLK_A64_USB_OHCI1>;
>
> On A64, EHCI requires the matched OHCI to work.
Ah, so just like on the H3 (where this also is needed
and not documented).
> And OHCI1 clock requires OHCI0 clock to work.
Hmm, that one is new, can you double check this ?
Regards,
Hans
>
> (But from the SoC's user manual we cannot get any infomation
> about the relationship between OHCI1 clock and OHCI0 clock,
> and in the manual OHCI0 clock is called OTG-OHCI)
>
> 01.08.2016, 15:01, "Arnd Bergmann" <arnd@arndb.de>:
>> On Sunday, July 31, 2016 7:25:36 PM CEST Icenowy Zheng wrote:
>>> Allwinner A64 EHCI requires 4 clocks to be enabled.
>>>
>>> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
>>
>> Can you say what those four clocks are?
>>
>> Are you sure that it's not just a case of a clock being
>> incorrectly described in the clk driver, i.e. you reference
>> one clock along with its parent here?
>>
>> Arnd
next prev parent reply other threads:[~2016-08-01 7:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 11:25 [PATCH 1/3] dt: bindings: add bindings for Allwinner A64 usb phy Icenowy Zheng
2016-07-31 11:25 ` [PATCH 2/3] phy: sun4i: add support for " Icenowy Zheng
2016-07-31 12:39 ` Amit Tomer
2016-07-31 13:18 ` Icenowy Zheng
2016-07-31 13:18 ` Icenowy Zheng
2016-07-31 14:39 ` Hans de Goede
2016-07-31 14:50 ` Chen-Yu Tsai
[not found] ` <CAGb2v65tbM=-4HthAiN2hLvKYCSQg_WDCXrFcAO94cohd1FfDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-31 15:24 ` Hans de Goede
2016-07-31 11:25 ` [PATCH 3/3] ehci-platform: add the max clock number to 4 Icenowy Zheng
2016-08-01 6:58 ` Arnd Bergmann
2016-08-01 7:05 ` Icenowy Zheng
2016-08-01 7:27 ` Hans de Goede [this message]
2016-08-01 8:18 ` Icenowy Zheng
2016-08-01 9:49 ` Hans de Goede
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=01a348da-3b26-68a6-9d9f-c37d81b4fd64@redhat.com \
--to=hdegoede@redhat.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.xyz \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=patchesrdh@mveas.com \
--cc=robh+dt@kernel.org \
--cc=stern@rowland.harvard.edu \
--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).