From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-pm@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-samsung-soc@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Pawel Moll <pawel.moll@arm.com>, Zhang Rui <rui.zhang@intel.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 1/3] thermal: exynos: List vtmu-supply as optional property in DT binding
Date: Tue, 8 Mar 2016 18:30:17 -0300 [thread overview]
Message-ID: <56DF4469.7090603@osg.samsung.com> (raw)
In-Reply-To: <20160308210744.GA8145@localhost.localdomain>
Hello Eduardo,
On 03/08/2016 06:07 PM, Eduardo Valentin wrote:
> On Thu, Feb 18, 2016 at 03:19:09PM -0300, Javier Martinez Canillas wrote:
>> The Exynos Thermal Management Unit binding says that the vtmu-supply
>> is optional but is listed in the required properties section. Add an
>> optional properties section and move the regulator property there.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>> ---
>>
>> Documentation/devicetree/bindings/thermal/exynos-thermal.txt | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
>> index faa62059b5c5..70b4c16c7ed8 100644
>> --- a/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
>> +++ b/Documentation/devicetree/bindings/thermal/exynos-thermal.txt
>> @@ -41,9 +41,6 @@
>> for current TMU channel
>> -- "tmu_sclk" clock for functional operation of the current TMU
>> channel
>> -- vtmu-supply: This entry is optional and provides the regulator node supplying
>> - voltage to TMU. If needed this entry can be placed inside
>> - board/platform specific dts file.
>>
>> The Exynos TMU supports generating interrupts when reaching given
>> temperature thresholds. Number of supported thermal trip points depends
>
> Where is this patch based on? I checked it on my fixes and linus
> branches, also on linux-next 0308 branch, and none of those apply clean.
>
I mentioned in the cover letter [0] that this series were based on top
of in-flight patches from Krzysztof Kozlowski to avoid merge conflicts.
Those have not landed yet either so maybe you could look at those first?
> Can you please send this based on upstream kernel?
>
Ok, my intention was to make picking both patch series easier but if
this is inconvenient to you, I can base on top of current mainline
and let you handle the merge conflicts (or ask Krzysztof to resend
on top of my patches).
[0]: https://lkml.org/lkml/2016/2/18/591
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-03-08 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:19 [PATCH 0/3] thermal: exynos: Fixes for vtmu-supply regulator handling Javier Martinez Canillas
2016-02-18 18:19 ` [PATCH 1/3] thermal: exynos: List vtmu-supply as optional property in DT binding Javier Martinez Canillas
2016-02-19 0:26 ` Krzysztof Kozlowski
2016-02-23 20:26 ` Rob Herring
2016-03-08 21:07 ` Eduardo Valentin
2016-03-08 21:30 ` Javier Martinez Canillas [this message]
2016-03-08 21:51 ` Eduardo Valentin
2016-02-18 18:19 ` [PATCH 2/3] thermal: exynos: Use devm_regulator_get_optional() for vtmu Javier Martinez Canillas
2016-02-19 0:33 ` Krzysztof Kozlowski
2016-02-18 18:19 ` [PATCH 3/3] thermal: exynos: Defer probe if vtmu is present but not registered Javier Martinez Canillas
2016-02-19 0:37 ` Krzysztof Kozlowski
2016-02-19 4:20 ` Andi Shyti
2016-02-19 4:25 ` Krzysztof Kozlowski
2016-02-19 4:29 ` [PATCH 0/3] thermal: exynos: Fixes for vtmu-supply regulator handling Andi Shyti
2016-03-08 13:30 ` Javier Martinez Canillas
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=56DF4469.7090603@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.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