public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>, Tawfik Bayouk <tawfik@marvell.com>,
	devicetree@vger.kernel.org, Lior Amsalem <alior@marvell.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v2 00/10] thermal: Armada 375/380 SoC support
Date: Fri, 25 Apr 2014 20:55:16 -0400	[thread overview]
Message-ID: <20140426005516.GR28159@titan.lakedaemon.net> (raw)
In-Reply-To: <1398371004-15807-1-git-send-email-ezequiel.garcia@free-electrons.com>

On Thu, Apr 24, 2014 at 05:23:14PM -0300, Ezequiel Garcia wrote:
> This patchset adds the support for the thermal sensor in the recently
> introduced Armada 375 and 38x SoC. Compared to the previous patchset
> version, this v2 introduces the A380 SoC support.
> 
> The first five patches are preparation work. They add a generic
> infrastructure that allows to support similar thermal sensors in
> a non-intrusive way.
> 
> Patches six and seven uses this infrastructure to support the 
> Armada 375 and 380 SoC thermal sensor.
> 
> Since there are some issues in the Armada 375 Z1 SoC thermal sensor,
> patch eight adds a quirk to workaround such issues. The Z1 silicon stepping
> is detected and the compatible string is updated, so the driver can apply
> sensor initialization workarounds.
> 
> In addition, the quirk moves the offset of the thermal control register,
> and allows to specifiy the correct (A0 stepping) offset in the devicetree.
> This quirk is applied only for the A375-DB board, being the only board known
> to have the problematic Z1 SoC.
> 
> Finally, the last two patches enables the thermal sensor in the devicetree.
> for the Armada 375 A0 stepping SoC, and the Armada 380/385 SoCs.
> 
> The series applies on v3.15-rc1, and has been tested on A375-DB board
> and A385-DB board.
> 
> Feedback and comments are welcome!
> 
> Changes from v1:
> 
>   * Introduced the Armada 380 support. In order to support this in a clean
>     way, the 'inverted' field was added.
> 
>   * Cleaned the A375 workaround in the thermal driver, by detecting the
>     device compatible string, as suggested by Jason Cooper.
> 
>   * Added details about the register offset in the Z1 stepping to the
>     binding documentation as requested by Jason Cooper.
> 
> Ezequiel Garcia (10):
>   thermal: armada: Rename armada_thermal_ops struct
>   thermal: armada: Add infrastructure to support generic formulas
>   thermal: armada: Add generic infrastructure to handle the sensor
>   thermal: armada: Pass the platform_device to init_sensor()
>   thermal: armada: Allow to specify an 'inverted readout' sensor
>   thermal: armada: Support Armada 375 SoC
>   thermal: armada: Support Armada 380 SoC

Thermal series:

Acked-by: Jason Cooper <jason@lakedaemon.net>

>   ARM: mvebu: Add thermal quirk for the Armada 375 DB board

Applied to mvebu/soc

>   ARM: mvebu: Enable the thermal sensor in Armada 375 SoC
>   ARM: mvebu: Enable the thermal sensor in Armada 380/385 SoC

Applied to mvebu/dt

thx,

Jason.

  parent reply	other threads:[~2014-04-26  0:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 20:23 [PATCH v2 00/10] thermal: Armada 375/380 SoC support Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 01/10] thermal: armada: Rename armada_thermal_ops struct Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 02/10] thermal: armada: Add infrastructure to support generic formulas Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 03/10] thermal: armada: Add generic infrastructure to handle the sensor Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 04/10] thermal: armada: Pass the platform_device to init_sensor() Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 05/10] thermal: armada: Allow to specify an 'inverted readout' sensor Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 06/10] thermal: armada: Support Armada 375 SoC Ezequiel Garcia
     [not found] ` <1398371004-15807-1-git-send-email-ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-24 20:23   ` [PATCH v2 07/10] thermal: armada: Support Armada 380 SoC Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 08/10] ARM: mvebu: Add thermal quirk for the Armada 375 DB board Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 09/10] ARM: mvebu: Enable the thermal sensor in Armada 375 SoC Ezequiel Garcia
2014-04-24 20:23 ` [PATCH v2 10/10] ARM: mvebu: Enable the thermal sensor in Armada 380/385 SoC Ezequiel Garcia
2014-04-28 16:44   ` Ezequiel Garcia
2014-04-28 18:33     ` Jason Cooper
2014-04-26  0:55 ` Jason Cooper [this message]
2014-04-26  1:45   ` [PATCH v2 00/10] thermal: Armada 375/380 SoC support Ezequiel Garcia

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=20140426005516.GR28159@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=alior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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