From: Stephen Boyd <sboyd@kernel.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, linux-mips@vger.kernel.org
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v3 1/3] clk: loongson1: add configuration option for loongson1 clks
Date: Wed, 06 Feb 2019 11:18:34 -0800 [thread overview]
Message-ID: <154948071478.115909.15205970894327083365@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190201063540.19636-2-jiaxun.yang@flygoat.com>
Quoting Jiaxun Yang (2019-01-31 22:35:38)
> diff --git a/drivers/clk/loongson1/Kconfig b/drivers/clk/loongson1/Kconfig
> new file mode 100644
> index 000000000000..e2220332d797
> --- /dev/null
> +++ b/drivers/clk/loongson1/Kconfig
> @@ -0,0 +1,27 @@
> +menu "Loongson-1 Clock drivers"
> + depends on MACH_LOONGSON32
> +
> +config LOONGSON1_CLOCK_COMMON
> + bool
> +
> +config LOONGSON1_CLOCK_LS1B
> + bool "Loongson 1B driver"
> + default y
Should be default CONFIG_LOONGSON1_LS1B?
> + select LOONGSON1_CLOCK_COMMON
Drop the selects and have the menuconfig make the "COMMON" config option
enabled then?
> + help
> + Support the clocks provided by the clock hardware on Loongson-1B
> + and compatible SoCs.
> +
> + If building for a Loongson-1B SoC, you want to say Y here.
> +
> +config LOONGSON1_CLOCK_LS1C
> + bool "Loongson 1C driver"
> + default y
And default CONFIG_LOONGSON1_LS1C?
> + select LOONGSON1_CLOCK_COMMON
> + help
> + Support the clocks provided by the clock hardware on Loongson-1C
> + and compatible SoCs.
> +
> + If building for a Loongson-1C SoC, you want to say Y here.
> +
> +endmenu
next prev parent reply other threads:[~2019-02-06 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 13:34 [PATCH 0/3] Enhance loongson-1 clock driver Jiaxun Yang
2019-01-25 13:34 ` [PATCH 1/3] clk: loongson1: add configuration option for loongson1 clks Jiaxun Yang
2019-01-25 13:34 ` [PATCH 2/3] clk: loongson1: add of support Jiaxun Yang
2019-01-25 13:34 ` [PATCH 3/3] dt-bindings: clock: Add loongson-1 clock bindings Jiaxun Yang
2019-01-28 15:20 ` [PATCH 0/3] Enhance loongson-1 clock driver Jiaxun Yang
2019-01-28 15:20 ` [PATCH v2 1/3] clk: loongson1: add configuration option for loongson1 clks Jiaxun Yang
2019-01-28 15:20 ` [PATCH v2 2/3] clk: loongson1: add of support Jiaxun Yang
2019-01-28 15:20 ` [PATCH v2 3/3] dt-bindings: clock: Add loongson-1 clock bindings Jiaxun Yang
2019-01-30 19:47 ` Rob Herring
2019-02-01 6:35 ` [PATCH v3 0/3] Enhance loongson-1 clock driver Jiaxun Yang
2019-02-01 6:35 ` [PATCH v3 1/3] clk: loongson1: add configuration option for loongson1 clks Jiaxun Yang
2019-02-06 19:18 ` Stephen Boyd [this message]
2019-02-01 6:35 ` [PATCH v3 2/3] clk: loongson1: add of support Jiaxun Yang
2019-02-06 19:16 ` Stephen Boyd
2019-02-01 6:35 ` [PATCH v3 3/3] dt-bindings: clock: Add loongson-1 clock bindings Jiaxun Yang
2019-02-13 22:56 ` Rob Herring
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=154948071478.115909.15205970894327083365@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.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).