From: Jon Hunter <jonathanh@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
<thierry.reding@gmail.com>, <robh+dt@kernel.org>
Cc: <mark.rutland@arm.com>, <linux-pwm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 4/4] pwm: tegra: Add support to configure pin state in suspends/resume
Date: Fri, 7 Apr 2017 08:51:54 +0100 [thread overview]
Message-ID: <38e8b3bf-404c-ddca-acf9-aab6248f61a7@nvidia.com> (raw)
In-Reply-To: <58E66F8F.1030802@nvidia.com>
On 06/04/17 17:40, Laxman Dewangan wrote:
> Oops, it was actually v2.
>
> On Thursday 06 April 2017 08:47 PM, Jon Hunter wrote:
>> On 06/04/17 15:21, Laxman Dewangan wrote:
>>> In some of NVIDIA Tegra's platform, PWM controller is used to
>>> control the PWM controlled regulators. PWM signal is connected to
>>> the VID pin of the regulator where duty cycle of PWM signal decide
>>> the voltage level of the regulator output.
>>>
>>> The tristate (high impedance of PWM pin form Tegra) also define
>>> one of the state of PWM regulator which needs to be configure in
>>> suspend state of system.
>>>
>>> Add support to configure the pin state via pinctrl frameworks in
>>> suspend and active state of the system.
>>>
>>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>>> ---
>>> Changes from v1:
>>> - Use standard pinctrl names for sleep and active state.
>>> - Use API pinctrl_pm_select_*()
>>>
>>> drivers/pwm/pwm-tegra.c | 22 ++++++++++++++++++++++
>>> 1 file changed, 22 insertions(+)
>>>
>>> diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
>>> index e9c4de5..af1bd4f 100644
>>> --- a/drivers/pwm/pwm-tegra.c
>>> +++ b/drivers/pwm/pwm-tegra.c
>>> @@ -29,6 +29,7 @@
>>> #include <linux/of_device.h>
>>> #include <linux/pwm.h>
>>> #include <linux/platform_device.h>
>>> +#include <linux/pinctrl/consumer.h>
>>> #include <linux/slab.h>
>>> #include <linux/reset.h>
>>> @@ -256,6 +257,22 @@ static int tegra_pwm_remove(struct
>>> platform_device *pdev)
>>> return pwmchip_remove(&pc->chip);
>>> }
>>> +#ifdef CONFIG_PM_SLEEP
>>> +static int tegra_pwm_suspend(struct device *dev)
>>> +{
>>> + pinctrl_pm_select_sleep_state(dev);
>> Why not return the error code here?
>
> As the pin state in suspend is optional, I dont want to return error if
> the sleep state is not available.
>
> However, it seems pinctrl take care of retuning success if there is no
> sleep state. By seeing code.
Exactly, that is what I did for i2c because pinctrl it is also optional
for i2c.
> Let me test this on different condition and it it works fine then we can
> return the return of pinctrl_pm_select_*()
>
>
> BTW, it should be OK to have pwm_tegra_resume/suspend wrapper, not
> directly use the pinctrl_pm_select_* in pm ops suspend/resume. The
> prototype matches.
I think that I would keep the wrapper.
>> By the way, do you plan to include patches to populate the bindings for
>> the pwm devices?
>
> I am planning to populate the GPU regulator which is PWM based. This
> will only populate the regulator.
Ok.
Jon
--
nvpublic
prev parent reply other threads:[~2017-04-07 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 14:20 [PATCH V2 0/4] pwm: tegra: Pin configuration in suspend/resume and cleanups Laxman Dewangan
2017-04-06 14:20 ` [PATCH V2 1/4] pwm: tegra: Use DIV_ROUND_CLOSEST_ULL() instead of local implementation Laxman Dewangan
2017-04-06 16:28 ` Thierry Reding
2017-04-06 14:20 ` [PATCH V2 2/4] pwm: tegra: Increase precision in pwm rate calculation Laxman Dewangan
2017-04-06 16:24 ` Thierry Reding
2017-04-06 16:28 ` Thierry Reding
2017-04-06 14:21 ` [PATCH V3 3/4] pwm: tegra: Add DT binding details to configure pin in suspends/resume Laxman Dewangan
2017-04-06 15:26 ` Jon Hunter
2017-04-06 16:48 ` Laxman Dewangan
2017-04-07 7:49 ` Jon Hunter
2017-04-06 14:21 ` [PATCH V4 4/4] pwm: tegra: Add support to configure pin state " Laxman Dewangan
2017-04-06 15:17 ` Jon Hunter
2017-04-06 16:40 ` Laxman Dewangan
2017-04-07 7:51 ` Jon Hunter [this message]
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=38e8b3bf-404c-ddca-acf9-aab6248f61a7@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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
Powered by JetHome