From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
lgirdwood@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] regulator: max8973: add support for junction thermal warning
Date: Wed, 6 Jan 2016 16:28:30 +0000 [thread overview]
Message-ID: <20160106162830.GZ6588@sirena.org.uk> (raw)
In-Reply-To: <20160106142521.GA11188@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
On Wed, Jan 06, 2016 at 08:25:21AM -0600, Rob Herring wrote:
> On Wed, Jan 06, 2016 at 12:37:35PM +0000, Mark Brown wrote:
> > > I tried to roundoff to the next higher threshold when supported value (120
> > > or 140 degC) is not provided in driver. But it is fine to me to specify the
> > > possible value setting here and DT binding doc. Will do on next patch.
> > I don't really mind which you use so long as the documentation is clear.
> I prefer that degrees are used rather than register values.
The downside of that is that it does mean more validation code.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-06 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 6:15 Laxman Dewangan
2016-01-06 12:18 ` Mark Brown
2016-01-06 12:19 ` Laxman Dewangan
2016-01-06 12:37 ` Mark Brown
2016-01-06 13:59 ` Laxman Dewangan
2016-01-06 14:25 ` Rob Herring
2016-01-06 14:20 ` Laxman Dewangan
2016-01-06 16:28 ` Mark Brown [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=20160106162830.GZ6588@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh@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
all inboxes | Powered by JetHome®