From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
Cc: Rob Herring <robh@kernel.org>,
linux-pwm@vger.kernel.org, lee.jones@linaro.org,
thierry.reding@gmail.com, p.zabel@pengutronix.de,
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 v6 1/2] Add DT bindings YAML schema for PWM fan controller of LGM SoC
Date: Wed, 12 Aug 2020 08:40:41 +0200 [thread overview]
Message-ID: <20200812064041.e75p5neq7wcg5dag@pengutronix.de> (raw)
In-Reply-To: <e50f198d-42d4-28b1-d32c-32f4b1bbcb0b@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
Hello Rahul,
On Wed, Aug 12, 2020 at 11:49:14AM +0800, Tanwar, Rahul wrote:
> Our PWM controller is actually a PWM fan controller dedicated for
> controlling fan. I am looking for some suggestions from you on how
> to handle fan related optional properties in such a scenario.
>
> Should i create a separate child node for fan with PWM node being
> the parent? Is that what you are suggesting? Thanks.
What is the problem of just using pwm-fan?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-12 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 8:52 [PATCH v6 0/2] pwm: intel: Add PWM driver for a new SoC Rahul Tanwar
2020-07-28 8:52 ` [PATCH v6 1/2] Add DT bindings YAML schema for PWM fan controller of LGM SoC Rahul Tanwar
2020-07-31 18:18 ` Rob Herring
2020-07-31 18:19 ` Rob Herring
2020-08-12 3:49 ` Tanwar, Rahul
2020-08-12 6:40 ` Uwe Kleine-König [this message]
2020-07-28 8:52 ` [PATCH v6 2/2] Add PWM fan controller driver for " Rahul Tanwar
2020-07-31 19:47 ` Uwe Kleine-König
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=20200812064041.e75p5neq7wcg5dag@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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=rahul.tanwar@linux.intel.com \
--cc=robh@kernel.org \
--cc=songjun.Wu@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).