From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 15/27] iommu/exynos: use convenient macro to handle gate clocks
Date: Fri, 14 Mar 2014 14:43:42 +0100 [thread overview]
Message-ID: <5323078E.4060903@samsung.com> (raw)
In-Reply-To: <20140314140951.3d443a3096e80297c9fecef0@samsung.com>
Hi KyongHo,
On 14.03.2014 06:09, Cho KyongHo wrote:
> exynos-iommu driver must care about master H/W's gate clock as well as
> System MMU's gate clock. To enhance readability of the source code,
> macros to gate/ungate those clocks are defined.
>
> Signed-off-by: Cho KyongHo <pullip.cho@samsung.com>
> ---
> drivers/iommu/exynos-iommu.c | 34 ++++++++++++++++++++++------------
> 1 file changed, 22 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
> index 71e77f1..cef62d0 100644
> --- a/drivers/iommu/exynos-iommu.c
> +++ b/drivers/iommu/exynos-iommu.c
> @@ -101,6 +101,16 @@
> #define REG_PB1_SADDR 0x054
> #define REG_PB1_EADDR 0x058
>
> +#define __clk_gate_ctrl(data, clk, en) do { \
> + if (data->clk) \
> + clk_##en##able(data->clk); \
> + } while (0)
> +
> +#define __sysmmu_clk_enable(data) __clk_gate_ctrl(data, clk, en)
> +#define __sysmmu_clk_disable(data) __clk_gate_ctrl(data, clk, dis)
> +#define __master_clk_enable(data) __clk_gate_ctrl(data, clk_master, en)
> +#define __master_clk_disable(data) __clk_gate_ctrl(data, clk_master, dis)
> +
I'd say that such macros only obfuscate code, without any gains, as you
can see in diffstat - this patch adds more lines than it removes.
Please drop this change.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-03-14 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 5:09 [PATCH v11 15/27] iommu/exynos: use convenient macro to handle gate clocks Cho KyongHo
2014-03-14 13:43 ` Tomasz Figa [this message]
2014-03-14 16:57 ` Sachin Kamat
2014-03-18 11:03 ` Cho KyongHo
2014-03-18 11:18 ` Sachin Kamat
2014-03-18 13:07 ` Tomasz Figa
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=5323078E.4060903@samsung.com \
--to=t.figa@samsung.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).