u-boot-amlogic.groups.io archive mirror
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: Alexey Romanov <avromanov@salutedevices.com>, narmstrong@baylibre.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de, kernel@sberdevices.ru
Subject: Re: [PATCH v1 1/2] clk: a1: add new clocks for USB stack
Date: Thu, 2 Nov 2023 14:36:12 +0100	[thread overview]
Message-ID: <74b52686-aed8-4a5f-bd35-bb286d27a937@linaro.org> (raw)
In-Reply-To: <20231101140500.9025-2-avromanov@salutedevices.com>

On 01/11/2023 15:04, Alexey Romanov wrote:
> Since we sync device tree with Linux, we have to add this
> clock definition for USB stack.
> 
> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> ---
>   drivers/clk/meson/a1.c | 6 ++++++
>   1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/clk/meson/a1.c b/drivers/clk/meson/a1.c
> index 1075ba7333..d0f5bb3753 100644
> --- a/drivers/clk/meson/a1.c
> +++ b/drivers/clk/meson/a1.c
> @@ -241,6 +241,12 @@ static const struct meson_clk_info *meson_clocks[] = {
>   	[CLKID_USB_PHY_IN] = CLK_GATE("usb_phy_in", A1_SYS_OSCIN_CTRL, 2,
>   		EXTERNAL_XTAL
>   	),
> +	[CLKID_USB_CTRL_IN] = CLK_GATE("usb_ctrl_in", A1_SYS_OSCIN_CTRL, 3,
> +		EXTERNAL_XTAL
> +	),
> +	[CLKID_USB_CTRL] = CLK_GATE("usb_ctrl", A1_SYS_CLK_EN0, 28,
> +		CLKID_SYS
> +	),
>   	[CLKID_USB_PHY] = CLK_GATE("usb_phy", A1_SYS_CLK_EN0, 27,
>   		CLKID_SYS
>   	),

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>


  reply	other threads:[~2023-11-02 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:04 [PATCH v1 0/2] Meson A1: fix USB and NAND stack Alexey Romanov
2023-11-01 14:04 ` [PATCH v1 1/2] clk: a1: add new clocks for USB stack Alexey Romanov
2023-11-02 13:36   ` neil.armstrong [this message]
2023-11-01 14:04 ` [PATCH v1 2/2] drivers: sm: bind child sm devices in the device tree Alexey Romanov
2023-11-02 13:36   ` neil.armstrong
2023-11-06  8:46 ` [PATCH v1 0/2] Meson A1: fix USB and NAND stack Neil Armstrong

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=74b52686-aed8-4a5f-bd35-bb286d27a937@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=avromanov@salutedevices.com \
    --cc=kernel@sberdevices.ru \
    --cc=narmstrong@baylibre.com \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.denx.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).