public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Shobhit Kumar <shobhit.kumar@intel.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 4/9] drivers/pwm: Add helper to configure pwm using clock divisor and duty percent
Date: Tue, 24 Mar 2015 09:23:59 +0100	[thread overview]
Message-ID: <20150324082357.GA17183@ulmo.nvidia.com> (raw)
In-Reply-To: <1426255082-25002-1-git-send-email-shobhit.kumar@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]

On Fri, Mar 13, 2015 at 07:28:02PM +0530, Shobhit Kumar wrote:
> Some chips instead of using period_ns and duty_ns can be configured
> using the clock divisor and duty percent. Adds an alternative
> configuration method for such chips

I don't see a need to introduce this alternative configuration
mechanism. Most, of not all, of the other drivers program a clock
divisor and some percentage of the duty cycle as well and it should be
easy to convert to that internally from the period and duty_cycle
parameters that you get in ->config().

Adding an alternative means of configuring the PWM also means that every
user driver now potentially needs to support both the traditional and
the alternative way because PWM providers may not implement both.

Thierry

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-24  8:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 16:31 [RFC v5 0/9] Crystalcove (CRC) PMIC based panel and pwm control Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 1/9] drivers/mfd: Add lookup table for Panel Control as GPIO signal Shobhit Kumar
2015-03-24  8:51   ` Thierry Reding
2015-03-24  9:37   ` Linus Walleij
2015-03-25 14:53   ` Linus Walleij
2015-03-12 16:31 ` [RFC v5 2/9] gpio/crystalcove: Add additional GPIO for Panel control Shobhit Kumar
2015-03-18 11:54   ` Linus Walleij
2015-03-25 14:51   ` Linus Walleij
2015-03-12 16:31 ` [RFC v5 3/9] drm/i915: Use the CRC gpio for panel enable/disable Shobhit Kumar
2015-03-13 14:29   ` Ville Syrjälä
2015-03-16  4:42     ` [PATCH " Shobhit Kumar
2015-03-18 12:19       ` Linus Walleij
2015-03-24  8:32         ` Daniel Vetter
2015-03-24  9:35           ` Linus Walleij
2015-03-24  9:50             ` Daniel Vetter
2015-03-24 10:16               ` Linus Walleij
2015-03-24 10:53                 ` Daniel Vetter
2015-03-25 12:24                   ` Linus Walleij
2015-03-25 13:13                     ` Daniel Vetter
2015-03-25 14:16                       ` Shobhit Kumar
2015-03-25 14:55                       ` Linus Walleij
2015-03-25 15:45                         ` Daniel Vetter
2015-03-12 16:31 ` [RFC v5 4/9] drivers/pwm: Add helper to configure pwm using clock divisor and duty percent Shobhit Kumar
2015-03-13 13:58   ` [PATCH " Shobhit Kumar
2015-03-24  8:23     ` Thierry Reding [this message]
2015-04-01  6:28       ` Shobhit Kumar
2015-04-10  8:29         ` Thierry Reding
2015-04-13  8:02           ` Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 5/9] drivers/mfd: Add PWM cell device for Crystalcove PMIC Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 6/9] drivers/pwm: Add Crystalcove (CRC) PWM driver Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 7/9] drivers/pwm: Remove __init initializer for pwm_add_table Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 8/9] drivers/mfd: ADD PWM lookup table for CRC PMIC based PWM Shobhit Kumar
2015-03-12 16:31 ` [RFC v5 9/9] drm/i915: Backlight control using CRC PMIC based PWM driver Shobhit Kumar
2015-03-13 14:30   ` Ville Syrjälä
2015-03-13 17:20     ` Daniel Vetter
2015-03-16  4:23       ` Shobhit Kumar
2015-03-16  4:33     ` Shobhit Kumar
2015-03-24  8:59     ` 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=20150324082357.GA17183@ulmo.nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=gnurou@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=sameo@linux.intel.com \
    --cc=shobhit.kumar@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