linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Qipeng Zha <qipeng.zha@intel.com>
Cc: linux-pwm@vger.kernel.org, mika.westerberg@intel.com
Subject: Re: [PATCH] pwm:lpss: update pwm setting for Broxton
Date: Thu, 12 Nov 2015 13:52:36 +0100	[thread overview]
Message-ID: <20151112125236.GD31671@ulmo> (raw)
In-Reply-To: <1447345684-108039-1-git-send-email-qipeng.zha@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1799 bytes --]

On Fri, Nov 13, 2015 at 12:28:04AM +0800, Qipeng Zha wrote:
> For Broxton PWM controller, base unit is defined as 8bit integer
> and 14bit fraction, so need to update base unit setting to output
> wave with right frequency.
> a) add scaler for each board setting;
> b) remove validity check of base unit for special board, let pwm
> user to handle this;
> 
> Signed-off-by: Qipeng Zha <qipeng.zha@intel.com>
> ---
>  drivers/pwm/pwm-lpss.c | 20 +++++++++++---------
>  drivers/pwm/pwm-lpss.h |  1 +
>  2 files changed, 12 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/pwm/pwm-lpss.c b/drivers/pwm/pwm-lpss.c
> index 2504410..5a907db 100644
> --- a/drivers/pwm/pwm-lpss.c
> +++ b/drivers/pwm/pwm-lpss.c
> @@ -14,6 +14,7 @@
>   */
>  
>  #include <linux/io.h>
> +#include <linux/time.h>
>  #include <linux/kernel.h>
>  #include <linux/module.h>
>  #include <linux/pm_runtime.h>
> @@ -24,11 +25,9 @@
>  #define PWM_ENABLE			BIT(31)
>  #define PWM_SW_UPDATE			BIT(30)
>  #define PWM_BASE_UNIT_SHIFT		8
> -#define PWM_BASE_UNIT_MASK		0x00ffff00
> +#define PWM_BASE_UNIT_MASK		0x3fffff00

Isn't this going to potentially write reserved bits on non-Broxton
platforms? Previously the upper 8 bits were masked out, but now only the
upper 2 bits are masked out. What about the other 6?

Perhaps it'd be better to parameterize the mask in a way similar to the
scaler value?

Also it's unclear to me how critical this is. Initial patches for
Broxton support were merged into Linus' tree yesterday. Presumably they
had received some testing before, but nobody can't have noticed or this
bug wouldn't exist in the patches that were merged. Does this break any
existing setups and hence should go into v4.4 along with the initial
Broxton support?

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-12 12:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 16:28 [PATCH] pwm:lpss: update pwm setting for Broxton Qipeng Zha
2015-11-12 12:52 ` Thierry Reding [this message]
2015-11-12 14:50   ` Mika Westerberg
2015-11-12 16:29     ` Thierry Reding

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=20151112125236.GD31671@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mika.westerberg@intel.com \
    --cc=qipeng.zha@intel.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).