linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: keystone: fix the clock node for mdio
Date: Mon, 3 Aug 2015 14:22:19 -0400	[thread overview]
Message-ID: <55BFB15B.8040207@ti.com> (raw)
In-Reply-To: <1438625518-21315-1-git-send-email-m-karicheri2@ti.com>

On 08/03/2015 02:11 PM, Murali Karicheri wrote:
> Currently the MDIO clock is pointing to clkpa instead of clkcpgmac.
> MDIO is part of the ethss and the clock should be clkcpgmac.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> ---
>   arch/arm/boot/dts/keystone.dtsi | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts/keystone.dtsi
> index e7a6f6d..6245a17 100644
> --- a/arch/arm/boot/dts/keystone.dtsi
> +++ b/arch/arm/boot/dts/keystone.dtsi
> @@ -273,7 +273,7 @@
>   			#size-cells = <0>;
>   			reg		= <0x02090300 0x100>;
>   			status = "disabled";
> -			clocks = <&clkpa>;
> +			clocks = <&clkcpgmac>;
>   			clock-names = "fck";
>   			bus_freq	= <2500000>;
>   		};
>
Santosh,

This is a big fix and needs to go in v4.2-rc. So please review and apply 
asap. v4.2 is the first release that has netcp driver fully functional 
and I want to fix as many known bugs as possible.

Thanks.

-- 
Murali Karicheri
Linux Kernel, Keystone

  parent reply	other threads:[~2015-08-03 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 18:11 [PATCH 1/2] ARM: dts: keystone: fix the clock node for mdio Murali Karicheri
2015-08-03 18:11 ` [PATCH 2/2] ARM: dts: keystone: Fix the mdio bindings by moving it to soc specific file Murali Karicheri
2015-08-03 18:22 ` Murali Karicheri [this message]
2015-08-03 18:30   ` [PATCH 1/2] ARM: dts: keystone: fix the clock node for mdio santosh.shilimkar at oracle.com
2015-08-03 18:50     ` Murali Karicheri
2015-08-03 19:00       ` santosh.shilimkar at oracle.com

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=55BFB15B.8040207@ti.com \
    --to=m-karicheri2@ti.com \
    --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).