From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] regulator: max8973: add support for junction thermal warning
Date: Fri, 12 Feb 2016 19:01:39 +0530 [thread overview]
Message-ID: <56BDDEBB.8060105@nvidia.com> (raw)
In-Reply-To: <CAL_JsqL1=WjdsXHNyKWxfAoe+8_4GjNzuKMKHpArR_ypppJ0Tw@mail.gmail.com>
On Friday 12 February 2016 07:06 PM, Rob Herring wrote:
> On Wed, Jan 6, 2016 at 10:07 AM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>
> Enhanced transient response (ETR) will affect the configuration of CKADV.
> +-maxim,junction-temp-warning: Junction temp warning on which device generates
> + warning interrupts. This is in millicelcius.
> Please append units: maxim,junction-temp-warning-millicelsius or
> perhaps maxim,junction-warn-millicelsius to shorten it a bit.
This is very generic which is there on most of PMIC devices from Maxim,
TI etc.
So can we make it generic i.e. do not prefix with vendor name like
"junction-warn-millicelsius"?
next prev parent reply other threads:[~2016-02-12 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 16:07 [PATCH V2] regulator: max8973: add support for junction thermal warning Laxman Dewangan
2016-01-06 18:12 ` Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown
2016-02-12 13:36 ` [PATCH V2] regulator: max8973: add support for junction thermal warning Rob Herring
2016-02-12 13:31 ` Laxman Dewangan [this message]
2016-02-12 14:04 ` Rob Herring
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=56BDDEBB.8060105@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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