From: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: u.kleine-koenig@pengutronix.de, linux-pwm@vger.kernel.org,
lee.jones@linaro.org, thierry.reding@gmail.com,
p.zabel@pengutronix.de, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
songjun.Wu@intel.com, cheol.yong.kim@intel.com,
qi-ming.wu@intel.com, rahul.tanwar.linux@gmail.com,
rtanwar@maxlinear.com
Subject: Re: [PATCH v7 0/2] pwm: intel: Add PWM driver for a new SoC
Date: Wed, 19 Aug 2020 12:16:01 +0800 [thread overview]
Message-ID: <37f7526e-5a04-1d27-347c-772fe085771e@linux.intel.com> (raw)
In-Reply-To: <20200818083852.GC1891694@smile.fi.intel.com>
Hi Andy,
On 18/8/2020 4:38 pm, Andy Shevchenko wrote:
> On Tue, Aug 18, 2020 at 01:48:59PM +0800, Rahul Tanwar wrote:
>> Patch 1 adds dt binding document in YAML format.
>> Patch 2 add PWM fan controller driver for LGM SoC.
>>
>> v7:
>> - Address code quality related review concerns.
>> - Rename fan related property to pwm-*.
>> - Fix one make dt_binding_check reported error.
> I guess it misses the answer why pwm-fan can't be integrated into the soup?
>
Can you please elaborate more? I could not understand your point clearly.
Regards,
Rahul
next prev parent reply other threads:[~2020-08-19 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 5:48 [PATCH v7 0/2] pwm: intel: Add PWM driver for a new SoC Rahul Tanwar
2020-08-18 5:49 ` [PATCH v7 1/2] Add DT bindings YAML schema for PWM fan controller of LGM SoC Rahul Tanwar
2020-08-18 5:49 ` [PATCH v7 2/2] Add PWM fan controller driver for " Rahul Tanwar
2020-08-18 8:38 ` [PATCH v7 0/2] pwm: intel: Add PWM driver for a new SoC Andy Shevchenko
2020-08-19 4:16 ` Tanwar, Rahul [this message]
2020-08-19 7:54 ` Andy Shevchenko
2020-08-19 8:46 ` 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=37f7526e-5a04-1d27-347c-772fe085771e@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=lee.jones@linaro.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=rtanwar@maxlinear.com \
--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;
as well as URLs for NNTP newsgroup(s).