From: caesar <caesar.wang@rock-chips.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: heiko@sntech.de, b.galvani@gmail.com, robh+dt@kernel.org,
ijc+devicetree@hellion.org.uk, rdunlap@infradead.org,
galak@codeaurora.org, cf@rock-chips.com, huangtao@rock-chips.com,
xjq@rock-chips.com, addy.ke@rock-chips.com, cjf@rock-chips.com,
hj@rock-chips.com, linux-arm-kernel@lists.infradead.org,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 2/2] pwm: rockchip: Added to support for RK3288 SoC
Date: Thu, 07 Aug 2014 21:55:24 +0800 [thread overview]
Message-ID: <53E3854C.9070005@rock-chips.com> (raw)
In-Reply-To: <20140807131443.GA1540@ulmo.nvidia.com>
Thierry,
在 2014年08月07日 21:14, Thierry Reding 写道:
> On Thu, Aug 07, 2014 at 09:04:30PM +0800, caesar wrote:
> [...]
>> As you say, I will rewrite the about if it's really need do so it.
>> For example:
>>
>> static const struct rockchip_pwm_data pwm_data_v1 = {
>> .regs = {
>> .duty = 0x04,
>> .period = 0x08,
>> .cntr = 0x00,
>> .ctrl = 0x0c,
>> },
>> .prescaler = 2,
>> .set_enable = rockchip_pwm_set_enable_v1,
>> };
>>
>> static const struct rockchip_pwm_data pwm_data_v2 = {
>> .regs = {
>> .duty = 0x08,
>> .period = 0x04,
>> .cntr = 0x00,
>> .ctrl = 0x0c,
>> },
>> .prescaler = 1,
>> .set_enable = rockchip_pwm_set_enable_v2,
>> };
>>
>> static const struct rockchip_pwm_data pwm_data_vop = {
>> .regs = {
>> .duty = 0x08,
>> .period = 0x04,
>> .cntr = 0x0c,
>> .ctrl = 0x00,
>> },
>> .prescaler = 1,
>> .set_enable = rockchip_pwm_set_enable_v2,
>> };
>>
>> Is that right?
> Yes.
>
>>>> + .set_enable = rockchip_pwm_set_enable_v2,
>>>> +};
>>> No need for the double indirection.
>> Sorry, I think is need if you mean a double indirection for ".set_enable".
> The "double indirection" was regarding the symbolic names for registers,
> not the .set_enable(). Sorry.
OK,I will fix the about in patch v5 tomorrow if no other problems,Thanks!
> Thierry
WARNING: multiple messages have this Message-ID (diff)
From: caesar.wang@rock-chips.com (caesar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] pwm: rockchip: Added to support for RK3288 SoC
Date: Thu, 07 Aug 2014 21:55:24 +0800 [thread overview]
Message-ID: <53E3854C.9070005@rock-chips.com> (raw)
In-Reply-To: <20140807131443.GA1540@ulmo.nvidia.com>
Thierry,
? 2014?08?07? 21:14, Thierry Reding ??:
> On Thu, Aug 07, 2014 at 09:04:30PM +0800, caesar wrote:
> [...]
>> As you say, I will rewrite the about if it's really need do so it.
>> For example:
>>
>> static const struct rockchip_pwm_data pwm_data_v1 = {
>> .regs = {
>> .duty = 0x04,
>> .period = 0x08,
>> .cntr = 0x00,
>> .ctrl = 0x0c,
>> },
>> .prescaler = 2,
>> .set_enable = rockchip_pwm_set_enable_v1,
>> };
>>
>> static const struct rockchip_pwm_data pwm_data_v2 = {
>> .regs = {
>> .duty = 0x08,
>> .period = 0x04,
>> .cntr = 0x00,
>> .ctrl = 0x0c,
>> },
>> .prescaler = 1,
>> .set_enable = rockchip_pwm_set_enable_v2,
>> };
>>
>> static const struct rockchip_pwm_data pwm_data_vop = {
>> .regs = {
>> .duty = 0x08,
>> .period = 0x04,
>> .cntr = 0x0c,
>> .ctrl = 0x00,
>> },
>> .prescaler = 1,
>> .set_enable = rockchip_pwm_set_enable_v2,
>> };
>>
>> Is that right?
> Yes.
>
>>>> + .set_enable = rockchip_pwm_set_enable_v2,
>>>> +};
>>> No need for the double indirection.
>> Sorry, I think is need if you mean a double indirection for ".set_enable".
> The "double indirection" was regarding the symbolic names for registers,
> not the .set_enable(). Sorry.
OK,I will fix the about in patch v5 tomorrow if no other problems,Thanks!
> Thierry
next prev parent reply other threads:[~2014-08-07 13:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 10:21 [PATCH v4 0/2] This series adds support for RK3288 SoC integrated PWM Caesar Wang
2014-07-24 10:21 ` Caesar Wang
2014-07-24 10:21 ` [PATCH v4 1/2] pwm: rockchip: document RK3288 SoC compatible Caesar Wang
2014-07-24 10:21 ` Caesar Wang
2014-07-24 10:21 ` [PATCH v4 2/2] pwm: rockchip: Added to support for RK3288 SoC Caesar Wang
2014-07-24 10:21 ` Caesar Wang
2014-08-06 22:46 ` Doug Anderson
2014-08-06 22:46 ` Doug Anderson
2014-08-07 1:27 ` caesar
2014-08-07 1:27 ` caesar
2014-08-07 2:16 ` Doug Anderson
2014-08-07 2:16 ` Doug Anderson
2014-08-07 3:23 ` caesar
2014-08-07 3:23 ` caesar
2014-08-07 3:26 ` Doug Anderson
2014-08-07 3:26 ` Doug Anderson
2014-08-07 3:37 ` caesar
2014-08-07 3:37 ` caesar
2014-08-07 3:46 ` Doug Anderson
2014-08-07 3:46 ` Doug Anderson
2014-08-07 4:05 ` caesar
2014-08-07 4:05 ` caesar
2014-08-07 6:12 ` Thierry Reding
2014-08-07 6:12 ` Thierry Reding
2014-08-07 6:18 ` Thierry Reding
2014-08-07 6:18 ` Thierry Reding
2014-08-07 13:04 ` caesar
2014-08-07 13:04 ` caesar
2014-08-07 13:04 ` caesar
2014-08-07 13:14 ` Thierry Reding
2014-08-07 13:14 ` Thierry Reding
2014-08-07 13:55 ` caesar [this message]
2014-08-07 13:55 ` caesar
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=53E3854C.9070005@rock-chips.com \
--to=caesar.wang@rock-chips.com \
--cc=addy.ke@rock-chips.com \
--cc=b.galvani@gmail.com \
--cc=cf@rock-chips.com \
--cc=cjf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=xjq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.