From: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-pwm@vger.kernel.org, thierry.reding@gmail.com,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, andriy.shevchenko@intel.com,
songjun.Wu@intel.com, cheol.yong.kim@intel.com,
qi-ming.wu@intel.com, rahul.tanwar.linux@gmail.com
Subject: Re: [PATCH v2 2/2] Add PWM fan controller driver for LGM SoC
Date: Thu, 25 Jun 2020 16:59:51 +0800 [thread overview]
Message-ID: <9a8f4a3e-c94a-b5bf-2715-03b0439f9fe7@linux.intel.com> (raw)
In-Reply-To: <20200625055818.nv5snblkm4nwvxw2@taurus.defre.kleine-koenig.org>
On 25/6/2020 1:58 pm, Uwe Kleine-König wrote:
> On Thu, Jun 25, 2020 at 12:23:54PM +0800, Tanwar, Rahul wrote:
>> Hi Philipp,
>>
>> On 18/6/2020 8:25 pm, Philipp Zabel wrote:
>>> Hi Rahul,
>>>
>>> On Thu, 2020-06-18 at 20:05 +0800, Rahul Tanwar wrote:
>>>> Intel Lightning Mountain(LGM) SoC contains a PWM fan controller.
>>>> This PWM controller does not have any other consumer, it is a
>>>> dedicated PWM controller for fan attached to the system. Add
>>>> driver for this PWM fan controller.
>>>>
>>>> Signed-off-by: Rahul Tanwar <rahul.tanwar@linux.intel.com>
>>>> ---
>>>> drivers/pwm/Kconfig | 9 +
>>>> drivers/pwm/Makefile | 1 +
>>>> drivers/pwm/pwm-intel-lgm.c | 400 ++++++++++++++++++++++++++++++++++++++++++++
>>>> 3 files changed, 410 insertions(+)
>>>> create mode 100644 drivers/pwm/pwm-intel-lgm.c
>>>>
>>> [...]
>>>> diff --git a/drivers/pwm/pwm-intel-lgm.c b/drivers/pwm/pwm-intel-lgm.c
>>>> new file mode 100644
>>>> index 000000000000..3c7077acb161
>>>> --- /dev/null
>>>> +++ b/drivers/pwm/pwm-intel-lgm.c
>>>> @@ -0,0 +1,400 @@
>>> [...]
>>>> +static int lgm_pwm_probe(struct platform_device *pdev)
>>>> +{
>>>> + struct lgm_pwm_chip *pc;
>>>> + struct device *dev = &pdev->dev;
>>>> + void __iomem *io_base;
>>>> + int ret;
>>>> +
>>>> + pc = devm_kzalloc(dev, sizeof(*pc), GFP_KERNEL);
>>>> + if (!pc)
>>>> + return -ENOMEM;
>>>> +
>>>> + io_base = devm_platform_ioremap_resource(pdev, 0);
>>>> + if (IS_ERR(io_base))
>>>> + return PTR_ERR(io_base);
>>>> +
>>>> + pc->regmap = devm_regmap_init_mmio(dev, io_base, &pwm_regmap_config);
>>>> + if (IS_ERR(pc->regmap)) {
>>>> + ret = PTR_ERR(pc->regmap);
>>>> + dev_err(dev, "failed to init register map: %pe\n", pc->regmap);
>>>> + return ret;
>>>> + }
>>>> +
>>>> + pc->clk = devm_clk_get(dev, NULL);
>>>> + if (IS_ERR(pc->clk)) {
>>>> + ret = PTR_ERR(pc->clk);
>>>> + dev_err(dev, "failed to get clock: %pe\n", pc->clk);
>>>> + return ret;
>>>> + }
>>>> +
>>>> + pc->rst = devm_reset_control_get(dev, NULL);
>>>> + if (IS_ERR(pc->rst)) {
>>>> + ret = PTR_ERR(pc->rst);
>>>> + dev_err(dev, "failed to get reset control: %pe\n", pc->rst);
>>>> + return ret;
>>>> + }
>>> Please use devm_reset_control_get_exclusive() to make it explicit an
>>> that exclusive reset control is requested. Given how the reset control
>>> is used, I think this driver could also use
>>> devm_reset_control_get_shared() to potentially allow sharing a reset
>>> line with other devices.
>> devm_reset_control_get() is a wrapper for devm_reset_control_get_exclusive().
>> Code as below:
>> static inline struct reset_control *devm_reset_control_get(
>> struct device *dev, const char *id)
>> {
>> return devm_reset_control_get_exclusive(dev, id);
>> }
>> Am i missing something else?
> Obviously you're missing the comment above of_reset_control_get about
> some functions being compatibility wrappers.
Oops, so sorry totally missed/overlooked that. Will update in v3. Thanks.
Regards,
Rahul
next prev parent reply other threads:[~2020-06-25 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 12:05 [PATCH v2 0/2] pwm: intel: Add PWM driver for a new SoC Rahul Tanwar
2020-06-18 12:05 ` [PATCH v2 1/2] Add DT bindings YAML schema for PWM fan controller of LGM SoC Rahul Tanwar
2020-06-19 6:14 ` Uwe Kleine-König
2020-06-18 12:05 ` [PATCH v2 2/2] Add PWM fan controller driver for " Rahul Tanwar
2020-06-18 12:25 ` Philipp Zabel
2020-06-25 4:23 ` Tanwar, Rahul
2020-06-25 5:58 ` Uwe Kleine-König
2020-06-25 8:59 ` Tanwar, Rahul [this message]
2020-06-19 6:02 ` Uwe Kleine-König
2020-06-19 6:29 ` Uwe Kleine-König
2020-06-25 7:28 ` Tanwar, Rahul
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=9a8f4a3e-c94a-b5bf-2715-03b0439f9fe7@linux.intel.com \
--to=rahul.tanwar@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar.linux@gmail.com \
--cc=robh+dt@kernel.org \
--cc=songjun.Wu@intel.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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