From: "Derald D. Woods" <woods.technical@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: t-kristo@ti.com, linux-clk@vger.kernel.org, sboyd@codeaurora.org,
mturquette@baylibre.com, linux-omap@vger.kernel.org,
tony@atomide.com, stable@vger.kernel.org
Subject: Re: [PATCH] clk: ti: omap3: Fix am3517 mdio clock alias
Date: Sat, 23 Jun 2018 09:38:43 -0500 [thread overview]
Message-ID: <20180623143824.GA14050@ethiopia> (raw)
In-Reply-To: <20180623110912.20633-1-aford173@gmail.com>
On Sat, Jun 23, 2018 at 06:09:12AM -0500, Adam Ford wrote:
> A previous patch removed OMAP clock aliases that were perceived
> to be unnecessary. Unfortunately, it broke the ethernet on the
> am3517-evm. This patch renables the MDIO clock.
>
> Fixes: 0ed266d7ae5e ("clk: ti: omap3: cleanup unnecessary clock aliases")
> Cc: stable@vger.kernel.org #4.16+
>
On AM3517-EVM, you can add:
Tested-by: Derald D. Woods <woods.technical@gmail.com>
> Signed-off-by: Adam Ford <aford173@gmail.com>
>
> diff --git a/drivers/clk/ti/clk-3xxx.c b/drivers/clk/ti/clk-3xxx.c
> index 8aa5f5793835..f84734bd0aa7 100644
> --- a/drivers/clk/ti/clk-3xxx.c
> +++ b/drivers/clk/ti/clk-3xxx.c
> @@ -254,6 +254,8 @@ static struct ti_dt_clk omap36xx_am35xx_omap3430es2plus_clks[] = {
> };
>
> static struct ti_dt_clk am35xx_clks[] = {
> + DT_CLK("davinci_emac.0", NULL, "emac_ick"),
> + DT_CLK("davinci_mdio.0", NULL, "emac_fck"),
> DT_CLK(NULL, "hsotgusb_ick", "hsotgusb_ick_am35xx"),
> DT_CLK(NULL, "hsotgusb_fck", "hsotgusb_fck_am35xx"),
> DT_CLK(NULL, "uart4_ick", "uart4_ick_am35xx"),
> --
> 2.17.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-23 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 11:09 [PATCH] clk: ti: omap3: Fix am3517 mdio clock alias Adam Ford
2018-06-23 14:38 ` Derald D. Woods [this message]
2018-06-25 6:26 ` Tero Kristo
2018-06-25 10:46 ` Adam Ford
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=20180623143824.GA14050@ethiopia \
--to=woods.technical@gmail.com \
--cc=aford173@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=stable@vger.kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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