All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Romain Izard <romain.izard.pro@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-pwm@vger.kernel.org,
	DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>
Subject: Re: [PATCH v3] pwm: add CSR SiRFSoC PWM driver
Date: Fri, 28 Feb 2014 22:33:02 +0800	[thread overview]
Message-ID: <CAGsJ_4yV-Dju2n-z=nG+Z0dyfwUdpJBN=sYGKn5SVYtMbX--6A@mail.gmail.com> (raw)
In-Reply-To: <CAGsJ_4wcmTEa0F=ELFCqF-MrRzuabYRTR-uctwCXqUJ7gdWRjw@mail.gmail.com>

>
> i think what we can make everything clear is making the channel clocks
> become clock nodes of the whole clock tree, the node can be requested
> by a non-PWM device and PWM-channel through clk_get. if someone wants
> a clock, get it from clock subsystem, and the PWM channel here can
> request the clock as well. but i don't have plan to do that for the
> moment.
>
i am not sure whether i have described everything clear enough. the
point is if the bluetooth want a clock with 32KHz, it should want it
by clk_get(), but not get it from pwm_config. it is just a workaround.
the pwm is the concept of prima2 hardware, lcd can think it is asking
pwm, why is bluetooth thinking it is requesting a PWM? in the view of
bluetooth, the source is a clock not a PWM thing for backlight.

-barry

WARNING: multiple messages have this Message-ID (diff)
From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] pwm: add CSR SiRFSoC PWM driver
Date: Fri, 28 Feb 2014 22:33:02 +0800	[thread overview]
Message-ID: <CAGsJ_4yV-Dju2n-z=nG+Z0dyfwUdpJBN=sYGKn5SVYtMbX--6A@mail.gmail.com> (raw)
In-Reply-To: <CAGsJ_4wcmTEa0F=ELFCqF-MrRzuabYRTR-uctwCXqUJ7gdWRjw@mail.gmail.com>

>
> i think what we can make everything clear is making the channel clocks
> become clock nodes of the whole clock tree, the node can be requested
> by a non-PWM device and PWM-channel through clk_get. if someone wants
> a clock, get it from clock subsystem, and the PWM channel here can
> request the clock as well. but i don't have plan to do that for the
> moment.
>
i am not sure whether i have described everything clear enough. the
point is if the bluetooth want a clock with 32KHz, it should want it
by clk_get(), but not get it from pwm_config. it is just a workaround.
the pwm is the concept of prima2 hardware, lcd can think it is asking
pwm, why is bluetooth thinking it is requesting a PWM? in the view of
bluetooth, the source is a clock not a PWM thing for backlight.

-barry

  reply	other threads:[~2014-02-28 14:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 10:23 [PATCH v3] pwm: add CSR SiRFSoC PWM driver Barry Song
2014-02-08 10:23 ` Barry Song
2014-02-26 14:10 ` Thierry Reding
2014-02-26 14:10   ` Thierry Reding
2014-02-26 16:01   ` Barry Song
2014-02-26 16:01     ` Barry Song
2014-02-26 16:19 ` Romain Izard
2014-02-26 16:19   ` Romain Izard
2014-02-27  2:49   ` Barry Song
2014-02-27  2:49     ` Barry Song
2014-02-27 10:51     ` Romain Izard
2014-02-27 10:51       ` Romain Izard
2014-02-28  3:01       ` Barry Song
2014-02-28  3:01         ` Barry Song
2014-02-28  5:30         ` Barry Song
2014-02-28  5:30           ` Barry Song
2014-02-28  9:06         ` Romain Izard
2014-02-28  9:06           ` Romain Izard
2014-02-28 10:07           ` Barry Song
2014-02-28 10:07             ` Barry Song
2014-02-28 10:33             ` Barry Song
2014-02-28 10:33               ` Barry Song
2014-02-28 13:36               ` Romain Izard
2014-02-28 13:36                 ` Romain Izard
2014-02-28 14:13                 ` Barry Song
2014-02-28 14:13                   ` Barry Song
2014-02-28 14:33                   ` Barry Song [this message]
2014-02-28 14:33                     ` Barry Song
2014-02-28 11:41             ` Romain Izard
2014-02-28 11:41               ` Romain Izard
2014-02-28 12:17               ` Barry Song
2014-02-28 12:17                 ` Barry Song

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='CAGsJ_4yV-Dju2n-z=nG+Z0dyfwUdpJBN=sYGKn5SVYtMbX--6A@mail.gmail.com' \
    --to=21cnbao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=romain.izard.pro@gmail.com \
    --cc=workgroup.linux@csr.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.