All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Kevin Smith <kevin.smith@elecsyscorp.com>
Cc: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"Gregory CLEMENT" <gregory.clement@free-electrons.com>
Subject: Re: [PATCH] clk: mvebu: Require corediv clock for Armada 38x
Date: Wed, 10 Feb 2016 22:28:21 +0100	[thread overview]
Message-ID: <20160210222821.51cfd91f@free-electrons.com> (raw)
In-Reply-To: <1455136849-7888-1-git-send-email-kevin.smith@elecsyscorp.com>

Dear Kevin Smith,

On Wed, 10 Feb 2016 20:41:13 +0000, Kevin Smith wrote:
> The corediv clock driver is required for the pxa3xx_nand driver,
> but is not included in the ARMADA_38X_CLK config.  Add
> MVEBU_CLK_COREDIV as a dependency of ARMADA_38X_CLK.
> 
> Without the corediv driver, nand initialization fails with the
> message:
> 
> pxa3xx-nand f10d0000.flash: failed to get nand clock
> pxa3xx-nand f10d0000.flash: alloc nand resource failed
> 
> With corediv enabled, flash is successfully detected.
> 
> Signed-off-by: Kevin Smith <kevin.smith@elecsyscorp.com>
> Cc: Michael Turquette <mturquette@baylibre.com>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>  drivers/clk/mvebu/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/clk/mvebu/Kconfig b/drivers/clk/mvebu/Kconfig
> index 2769625..1107056 100644
> --- a/drivers/clk/mvebu/Kconfig
> +++ b/drivers/clk/mvebu/Kconfig
> @@ -20,6 +20,7 @@ config ARMADA_375_CLK
>  config ARMADA_38X_CLK
>  	bool
>  	select MVEBU_CLK_COMMON
> +	select MVEBU_CLK_COREDIV

Thanks for the patch!

I believe there are some more issues in this Kconfig file:

 - The ARMADA_XP_CLK option selects MVEBU_CLK_COREDIV but there is no
   corediv clock on Armada XP.

 - The ARMADA_375_CLK should also select MVEBU_CLK_COREDIV.

However, technically speaking, building ARMADA_38X_CLK or
ARMADA_375_CLK does not require building clk-corediv.c, it only needs
common.c. So maybe instead we should change arch/arm/mach-mvebu/Kconfig
to have MACH_ARMADA_xxx select MVEBU_CLK_COREDIV when needed.

But maybe I'm being overly pedantic here, and your solution is good
enough. I don't have a strong opinion on this.

But if we go with your solution, then I'd like to fix the Armada XP and
Armada 375 cases as well.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-02-10 21:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 20:41 [PATCH] clk: mvebu: Require corediv clock for Armada 38x Kevin Smith
2016-02-10 21:28 ` Thomas Petazzoni [this message]
2016-02-10 23:38   ` Kevin Smith
2016-02-10 23:40 ` [PATCH v2 1/2] clk: mvebu: Remove corediv clock from Armada XP Kevin Smith
2016-02-10 23:40   ` [PATCH v2 2/2] clk: mvebu: Move corediv config to mvebu config Kevin Smith
2016-02-11  8:16     ` Thomas Petazzoni
2016-02-11 16:01       ` Kevin Smith
2016-02-11 16:04         ` Thomas Petazzoni
2016-02-11 16:10           ` Kevin Smith
2016-02-11 16:53 ` [PATCH v3 1/2] clk: mvebu: Remove corediv clock from Armada XP Kevin Smith
2016-02-11 16:54   ` [PATCH v3 2/2] clk: mvebu: Move corediv config to mvebu config Kevin Smith
2016-02-12 16:28     ` Gregory CLEMENT
2016-02-18  1:16     ` Michael Turquette
2016-02-25 23:06     ` Stephen Boyd
2016-02-12 16:28   ` [PATCH v3 1/2] clk: mvebu: Remove corediv clock from Armada XP Gregory CLEMENT
2016-02-18  1:16   ` Michael Turquette
2016-02-18  8:11     ` Thomas Petazzoni
2016-02-18 17:54       ` Gregory CLEMENT
2016-02-25 23:06   ` Stephen Boyd

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=20160210222821.51cfd91f@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=kevin.smith@elecsyscorp.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.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 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.