linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] pwm: rockchip: Added to support for RK3288 SoC
Date: Thu, 7 Aug 2014 15:14:44 +0200	[thread overview]
Message-ID: <20140807131443.GA1540@ulmo.nvidia.com> (raw)
In-Reply-To: <53E3795E.4080607@rock-chips.com>

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.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140807/d1950544/attachment.sig>

  reply	other threads:[~2014-08-07 13:14 UTC|newest]

Thread overview: 16+ 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 ` [PATCH v4 1/2] pwm: rockchip: document RK3288 SoC compatible Caesar Wang
2014-07-24 10:21 ` [PATCH v4 2/2] pwm: rockchip: Added to support for RK3288 SoC Caesar Wang
2014-08-06 22:46   ` Doug Anderson
2014-08-07  1:27     ` caesar
2014-08-07  2:16       ` Doug Anderson
2014-08-07  3:23         ` caesar
2014-08-07  3:26           ` Doug Anderson
2014-08-07  3:37             ` caesar
2014-08-07  3:46               ` Doug Anderson
2014-08-07  4:05                 ` caesar
2014-08-07  6:12             ` Thierry Reding
2014-08-07  6:18   ` Thierry Reding
2014-08-07 13:04     ` caesar
2014-08-07 13:14       ` Thierry Reding [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=20140807131443.GA1540@ulmo.nvidia.com \
    --to=thierry.reding@gmail.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).