From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: Andy Yan <andy.yan@rock-chips.com>,
devicetree@vger.kernel.org, shawn.lin@rock-chips.com,
zhangqing@rock-chips.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 01/14] clk: rockchip: add more clk ids for rv1108
Date: Tue, 01 Aug 2017 01:27:45 +0200 [thread overview]
Message-ID: <3065556.yAAG1ix4ad@phil> (raw)
In-Reply-To: <1501495602-21351-1-git-send-email-andy.yan@rock-chips.com>
Hi Andy,
Am Montag, 31. Juli 2017, 18:06:42 CEST schrieb Andy Yan:
> From: Elaine Zhang <zhangqing@rock-chips.com>
>
> Added the missing clock ids, make the clock more complete.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
this clock-id patch is way to overloaded. Please split into 3 parts:
- completely new clock-ids
- changes to existing clock-ids
This also needs a very good reasoning, as such constant ids are
considered part of api and should not change to prevent breakage
with old devicetrees. So please double-check if the rename is really
necessary.
- cosmetics ... aka the indentation stuff
[...]
> /* aclk gates */
> #define ACLK_DMAC 192
> -#define ACLK_PRE 193
> +#define ACLK_BUS 193
This is one such case where you need a very good reason
[...]
> @@ -59,18 +120,30 @@
> #define PCLK_I2C2 261
> #define PCLK_I2C3 262
> #define PCLK_SPI 263
> -#define PCLK_SFC 264
why is this clock going away?
> #define PCLK_UART0 265
> #define PCLK_UART1 266
> #define PCLK_UART2 267
> #define PCLK_TSADC 268
> -#define PCLK_PWM 269
> +#define PCLK_PWM1 269
In your pwm patch, all blocks use the same clocks, so
this rename should be unnecessary
> /* hclk gates */
> #define HCLK_I2S0_8CH 320
> -#define HCLK_I2S1_8CH 321
> +#define HCLK_I2S1_2CH 321
Again reasoning required (that i2s1 has 2 channels
but not 8 should be ok for that)
> #define HCLK_I2S2_2CH 322
> #define HCLK_NANDC 323
> #define HCLK_SDMMC 324
Heiko
next prev parent reply other threads:[~2017-07-31 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:04 [PATCH 00/14] Support more devices on rockchip rv1108 Andy Yan
2017-07-31 10:06 ` [PATCH 01/14] clk: rockchip: add more clk ids for rv1108 Andy Yan
2017-07-31 23:27 ` Heiko Stuebner [this message]
2017-07-31 10:08 ` [PATCH 02/14] clk: rockchip: support more clks " Andy Yan
2017-07-31 23:31 ` Heiko Stuebner
2017-07-31 10:10 ` [PATCH 03/14] pinctrl: rockchip: add input schmitt support " Andy Yan
2017-07-31 11:26 ` Heiko Stübner
2017-08-07 8:49 ` Linus Walleij
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=3065556.yAAG1ix4ad@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=zhangqing@rock-chips.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;
as well as URLs for NNTP newsgroup(s).