From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Abhilash Kesavan <a.kesavan@samsung.com>
Cc: tomasz.figa@gmail.com, kgene.kim@samsung.com,
k.kozlowski@samsung.com, b.zolnierkie@samsung.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] clk: samsung: cpu: Prepare for addition for Exynos7 CPU clocks
Date: Thu, 07 Jul 2016 12:45:57 +0200 [thread overview]
Message-ID: <577E32E5.4010902@samsung.com> (raw)
In-Reply-To: <1467750561-13957-2-git-send-email-a.kesavan@samsung.com>
On 07/05/2016 10:29 PM, Abhilash Kesavan wrote:
> Exynos7 has the same CPU clock registers layout as that present
> in Exynos5433 except for the bits in the MUX_STAT* registers.
> Add a new CLK_CPU_HAS_MODIFIED_MUX_STAT flag to handle this change.
> --- a/drivers/clk/samsung/clk-cpu.h
> +++ b/drivers/clk/samsung/clk-cpu.h
> @@ -63,6 +63,8 @@ struct exynos_cpuclk {
> /* The CPU clock registers have Exynos5433-compatible layout */
> #define CLK_CPU_HAS_E5433_REGS_LAYOUT (1 << 2)
> +/* Exynos5433-compatible layout with different MUX_STAT register bits */
> +#define CLK_CPU_HAS_MODIFIED_MUX_STAT (1 << 3)
It's getting a bit messy, what if there comes another SoC version
which has some other modification of exynos5433 registers structure?
We would need another variant of HAS_MODIFIED_MUX_STAT flag and we
could easily get lost while trying to determine which modification
is which. How about indicating explicitly it's an exynos7 bits
layout and renaming the flag to something like
#define CLK_CPU_HAS_E7_MUX_STAT (1 << 16) ?
next prev parent reply other threads:[~2016-07-07 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 20:29 [PATCH v3 0/2] Add CPU clock support for Exynos7 Abhilash Kesavan
2016-07-05 20:29 ` [PATCH v3 1/2] clk: samsung: cpu: Prepare for addition for Exynos7 CPU clocks Abhilash Kesavan
2016-07-07 10:45 ` Sylwester Nawrocki [this message]
2016-07-07 11:17 ` Bartlomiej Zolnierkiewicz
2016-07-11 14:44 ` Abhilash Kesavan
2016-07-12 13:44 ` Bartlomiej Zolnierkiewicz
2016-07-11 14:44 ` Abhilash Kesavan
2016-07-05 20:29 ` [PATCH v3 2/2] clk: samsung: exynos7: Add clocks for atlas block Abhilash Kesavan
2016-07-05 18:56 ` kbuild test robot
2016-07-07 10:26 ` Sylwester Nawrocki
2016-07-11 14:43 ` Abhilash Kesavan
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=577E32E5.4010902@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=tomasz.figa@gmail.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