From: xuejiancheng <xuejiancheng@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
mturquette@baylibre.com, sboyd@codeaurora.org,
xuwei5@hisilicon.com, haojian.zhuang@linaro.org,
zhangfei.gao@linaro.org, bintian.wang@huawei.com,
yanhaifeng@hisilicon.com, yanghongwei@hisilicon.com,
suwenping@hisilicon.com, ml.yang@hisilicon.com,
gaofei@hisilicon.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 1/9] clk: hi3519: add dt-binding document and header file
Date: Fri, 4 Dec 2015 11:21:28 +0800 [thread overview]
Message-ID: <566106B8.7080205@huawei.com> (raw)
In-Reply-To: <1615805.jmP28L2rmX@wuerfel>
Hi Arnd,
On 2015/12/3 17:44, Arnd Bergmann wrote:
> On Thursday 03 December 2015 10:39:24 Jiancheng Xue wrote:
>> +#ifndef __DTS_HI3519_CLOCK_H
>> +#define __DTS_HI3519_CLOCK_H
>
> Please try to avoid adding headers like this if you can at all.
>
> I might ask you to merge the header file in one merge window
> otherwise and submit the platform code one kernel later, as they
> tendn to cause us needless dependencies otherwise.
>
Sorry. In v1, Rob suggested putting binding doc and header files in
a separate patch. The clock driver indeed depends on the header.
I will put the header and the clock driver in a patch, and keep the
binding doc in another patch.
>
>> +/* fixed rate */
>> +#define HI3519_FIXED_400M 1
>> +#define HI3519_FIXED_200M 2
>> +#define HI3519_FIXED_125M 3
>> +#define HI3519_FIXED_150M 4
>> +#define HI3519_FIXED_75M 5
>> +#define HI3519_FIXED_300M 6
>> +#define HI3519_FIXED_50M 7
>> +#define HI3519_FIXED_24M 8
>> +#define HI3519_FIXED_3M 9
>> +
>> +/* mux clocks */
>> +#define HI3519_FMC_MUX 32
>> +#define HI3519_I2C_MUX 33
>> +#define HI3519_UART_MUX 34
>> +#define HI3519_SYSAXI_MUX 35
>> +
>> +/*fixed factor clocks*/
>> +#define HI3519_SYSAPB_CLK 64
>> +
>> +/* gate clocks */
>> +#define HI3519_FMC_CLK 129
>> +#define HI3519_UART0_CLK 153
>> +#define HI3519_UART1_CLK 154
>> +#define HI3519_UART2_CLK 155
>> +#define HI3519_UART3_CLK 156
>> +#define HI3519_UART4_CLK 157
>
> Where do those numbers come from? They are not consecutive, so it sounds
> like they are directly from the data sheet and won't be needed in the driver.
> If that's true, just use the numbers directly, as you do for everything
> else.
The numbers are defined by myself, not directly from the data sheet. Some numbers
are reserved for device nodes which will be added later. So they are not consecutive now.
>
>> +#define HI3519_NR_CLKS 256
>> +#define HI3519_NR_RSTS 256
>>
> These seem to not be needed at all.
These are used in drivers/clk/hisilicon/clk-hi3519.c.
>
> Arnd
>
> .
>
next prev parent reply other threads:[~2015-12-04 3:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 2:39 [PATCH v2 1/9] clk: hi3519: add dt-binding document and header file Jiancheng Xue
2015-12-03 9:44 ` Arnd Bergmann
2015-12-04 3:21 ` xuejiancheng [this message]
2015-12-04 10:56 ` Arnd Bergmann
2015-12-07 8:01 ` xuejiancheng
2015-12-07 9:36 ` Arnd Bergmann
2015-12-08 1:37 ` xuejiancheng
2015-12-08 9:45 ` xuejiancheng
2015-12-08 10:23 ` Arnd Bergmann
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=566106B8.7080205@huawei.com \
--to=xuejiancheng@huawei.com \
--cc=arnd@arndb.de \
--cc=bintian.wang@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gaofei@hisilicon.com \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ml.yang@hisilicon.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=suwenping@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangfei.gao@linaro.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).