linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] usb: misc: generic_onboard_hub: add generic onboard USB HUB driver
Date: Wed, 09 Dec 2015 10:13:11 +0100	[thread overview]
Message-ID: <1449652391.3118.24.camel@pengutronix.de> (raw)
In-Reply-To: <20151209085959.GG941@shlinux2>

Am Mittwoch, den 09.12.2015, 17:00 +0800 schrieb Peter Chen:
> On Wed, Dec 09, 2015 at 09:57:40AM +0100, Lucas Stach wrote:
> > Am Mittwoch, den 09.12.2015, 16:50 +0800 schrieb Peter Chen:
> > > On Tue, Dec 08, 2015 at 08:36:00AM -0700, Mathieu Poirier wrote:
> > > > On 7 December 2015 at 18:37, Peter Chen <peter.chen@freescale.com> wrote:
> > > > > +
> > > > > +       if (dev->of_node) {
> > > > > +               struct device_node *node = dev->of_node;
> > > > > +
> > > > > +               hub_data->clk = devm_clk_get(dev, "external_clk");
> > > > > +               if (IS_ERR(hub_data->clk)) {
> > > > > +                       dev_dbg(dev, "Can't get external clock: %ld\n",
> > > > > +                                       PTR_ERR(hub_data->clk));
> > > > > +               }
> > > > 
> > > > Is the intended behaviour to keep going here event when there is an
> > > > error?  Can the "hub_data" really work without a clock?
> > > 
> > > Yes, some HUB may work with fixed 24M OSC at the board, but they need to
> > > reset through external IO, so the clock is not need at this case, but
> > > reset pin is mandatory.
> > > 
> > If the hub always requires a clock it must not be optional. If you have
> > a fixed 24MHz clock on board add this to the DT as a fixed-clock and use
> > it as an input to the hub.
> > 
> 
> This fixed 24MHz clock may from a fixed crystal on board, it is always
> on, no software need to control it, imx51-bbg board is an example.
> 
And that's wh it is a fixed-clock. Please look it up in the DT binding
documentation.
-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |

  reply	other threads:[~2015-12-09  9:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  1:37 [PATCH 0/3] USB: add generic onboard USB HUB driver Peter Chen
2015-12-08  1:37 ` [PATCH 1/3] usb: misc: generic_onboard_hub: " Peter Chen
2015-12-08  2:59   ` Felipe Balbi
2015-12-08  9:18     ` Peter Chen
2015-12-08 13:55       ` Felipe Balbi
2015-12-09  8:45         ` Peter Chen
2015-12-08  3:16   ` kbuild test robot
2015-12-08  9:36     ` Peter Chen
2015-12-08  6:19   ` Sascha Hauer
2015-12-08  9:26     ` Peter Chen
2015-12-08  9:44       ` Sascha Hauer
2015-12-09  8:23         ` Peter Chen
2015-12-08  9:48   ` Arnd Bergmann
2015-12-09  8:14     ` Peter Chen
2015-12-08 15:36   ` Mathieu Poirier
2015-12-09  8:50     ` Peter Chen
2015-12-09  8:57       ` Lucas Stach
2015-12-09  9:00         ` Peter Chen
2015-12-09  9:13           ` Lucas Stach [this message]
2015-12-09  9:29             ` Peter Chen
2015-12-09  9:10         ` Arnd Bergmann
2015-12-09  9:08           ` Peter Chen
2015-12-08  1:37 ` [PATCH 2/3] doc: dt-binding: generic onboard USB HUB Peter Chen
2015-12-08  2:30   ` Fabio Estevam
2015-12-08  9:20     ` Peter Chen
2015-12-08  9:45       ` Arnd Bergmann
2015-12-08  9:50   ` Philipp Zabel
2015-12-08  9:58     ` Arnd Bergmann
2015-12-09  3:24       ` Rob Herring
2015-12-09  8:12         ` Peter Chen
2015-12-09  8:55           ` Arnd Bergmann
2015-12-15 20:21             ` Ulf Hansson
2015-12-16  2:46               ` Peter Chen
2015-12-09  8:09     ` Peter Chen
2015-12-08  1:37 ` [PATCH 3/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen

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=1449652391.3118.24.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).