From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 13/24] input: misc: max8997: explicitly apply PWM config extracted from pwm_args
Date: Sun, 17 Apr 2016 05:45:48 -0700 [thread overview]
Message-ID: <20160417124548.GE33215@dtor-ws> (raw)
In-Reply-To: <1460661464-11216-14-git-send-email-boris.brezillon@free-electrons.com>
On Thu, Apr 14, 2016 at 09:17:33PM +0200, Boris Brezillon wrote:
> Call pwm_apply_args() just after requesting the PWM device so that the
> polarity and period are initialized according to the information provided
> in pwm_args.
>
> This is an intermediate state, and pwm_apply_args() should be dropped as
> soon as the atomic PWM infrastructure is in place and the driver makes
> use of it.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> drivers/input/misc/max8997_haptic.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/input/misc/max8997_haptic.c b/drivers/input/misc/max8997_haptic.c
> index a806ba3..bf17f65 100644
> --- a/drivers/input/misc/max8997_haptic.c
> +++ b/drivers/input/misc/max8997_haptic.c
> @@ -304,6 +304,12 @@ static int max8997_haptic_probe(struct platform_device *pdev)
> error);
> goto err_free_mem;
> }
> +
> + /*
> + * FIXME: pwm_apply_args() should be removed when switching to
> + * the atomic PWM API.
> + */
> + pwm_apply_args(chip->pwm);
I do not understand. We did not fetch/modify any args, what are we
applying and why? Especially since we saying we want to remove this
later.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-04-17 12:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 19:17 [PATCH v5 00/24] pwm: add support for atomic update Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 01/24] pwm: introduce the pwm_args concept Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 02/24] pwm: use pwm_get/set_xxx() helpers where appropriate Boris Brezillon
2016-04-14 19:24 ` Joachim Eastwood
2016-04-14 19:17 ` [PATCH v5 03/24] clk: pwm: use pwm_get_args() " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 04/24] hwmon: pwm-fan: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 05/24] input: misc: max77693: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 06/24] leds: pwm: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 07/24] regulator: " Boris Brezillon
2016-04-15 6:54 ` Mark Brown
2016-04-14 19:17 ` [PATCH v5 08/24] fbdev: ssd1307fb: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 09/24] backlight: pwm_bl: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 10/24] backlight: lp8788: explicitly apply PWM config extracted from pwm_args Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 11/24] backlight: lp855x: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 12/24] backlight: lm3630a: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 13/24] input: misc: max8997: " Boris Brezillon
2016-04-17 12:45 ` Dmitry Torokhov [this message]
2016-04-17 15:39 ` Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 14/24] input: misc: pwm-beeper: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 15/24] drm: i915: " Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 16/24] ARM: " Boris Brezillon
2016-04-15 8:17 ` Krzysztof Kozlowski
2016-04-14 19:17 ` [PATCH v5 17/24] pwm: keep PWM state in sync with hardware state Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 18/24] pwm: introduce the pwm_state concept Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 19/24] pwm: move the enabled/disabled info into pwm_state Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 20/24] pwm: add the PWM initial state retrieval infra Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 21/24] pwm: add the core infrastructure to allow atomic update Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 22/24] pwm: update documentation Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 23/24] pwm: switch to the atomic API Boris Brezillon
2016-04-14 19:17 ` [PATCH v5 24/24] pwm: add information about polarity, duty cycle and period to debugfs Boris Brezillon
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=20160417124548.GE33215@dtor-ws \
--to=dmitry.torokhov@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