From: Matthias Kaehlcke <mka@chromium.org>
To: Frieder Schrempf <frieder@fris.de>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
"Frieder Schrempf" <frieder.schrempf@kontron.de>,
"Anand Moon" <linux.amoon@gmail.com>,
"Benjamin Bara" <benjamin.bara@skidata.com>,
"Rob Herring" <robh@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [RESEND PATCH v2 2/3] usb: misc: onboard_usb_hub: Add support for clock input
Date: Fri, 1 Dec 2023 20:08:36 +0000 [thread overview]
Message-ID: <ZWo0ZjKDsZKa6RyA@google.com> (raw)
In-Reply-To: <20231127112234.109073-2-frieder@fris.de>
On Mon, Nov 27, 2023 at 12:22:25PM +0100, Frieder Schrempf wrote:
> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>
> Most onboard USB hubs have a dedicated crystal oscillator but on some
> boards the clock signal for the hub is provided by the SoC.
>
> In order to support this, we add the possibility of specifying a
> clock in the devicetree that gets enabled/disabled when the hub
> is powered up/down.
>
> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
Acked-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2023-12-01 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 11:22 [RESEND PATCH v2 1/3] usb: misc: onboard_usb_hub: Print symbolic error names Frieder Schrempf
2023-11-27 11:22 ` [RESEND PATCH v2 2/3] usb: misc: onboard_usb_hub: Add support for clock input Frieder Schrempf
2023-12-01 20:08 ` Matthias Kaehlcke [this message]
2023-11-27 11:22 ` [RESEND PATCH v2 3/3] usb: misc: onboard_usb_hub: Add support for Cypress CY7C6563x Frieder Schrempf
2023-12-01 20:31 ` Matthias Kaehlcke
2023-12-01 19:27 ` [RESEND PATCH v2 1/3] usb: misc: onboard_usb_hub: Print symbolic error names Matthias Kaehlcke
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=ZWo0ZjKDsZKa6RyA@google.com \
--to=mka@chromium.org \
--cc=benjamin.bara@skidata.com \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.