public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Zhang Rui <rui.zhang@intel.com>, linux-pm@vger.kernel.org
Cc: Jason Cooper <jason@lakedaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v3 0/7] thermal: Armada 375/380 SoC support
Date: Tue, 6 May 2014 14:31:57 -0300	[thread overview]
Message-ID: <20140506173157.GA22929@arch.cereza> (raw)
In-Reply-To: <1399395591-5713-1-git-send-email-ezequiel.garcia@free-electrons.com>

Just a minor clarification:

On 06 May 01:59 PM, 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, only the driver changes are being sent now. The rest has been
> merged by Jason Cooper through the mvebu tree.
> 
> There are other very minor changes from v2, see below.
> 
> 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.
> 

Of course, the current series end right here, in patch seven...

> 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.
> 

.. the quirk patch has been already merged through mvebu.

Thanks and sorry for the noise!

Zhang: Any comments about the driver changes?
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  parent reply	other threads:[~2014-05-06 17:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 16:59 [PATCH v3 0/7] thermal: Armada 375/380 SoC support Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 1/7] thermal: armada: Rename armada_thermal_ops struct Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 2/7] thermal: armada: Add infrastructure to support generic formulas Ezequiel Garcia
2014-05-15  0:07   ` Eduardo Valentin
2014-05-06 16:59 ` [PATCH v3 3/7] thermal: armada: Add generic infrastructure to handle the sensor Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 4/7] thermal: armada: Pass the platform_device to init_sensor() Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 5/7] thermal: armada: Allow to specify an 'inverted readout' sensor Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 6/7] thermal: armada: Support Armada 375 SoC Ezequiel Garcia
2014-05-06 16:59 ` [PATCH v3 7/7] thermal: armada: Support Armada 380 SoC Ezequiel Garcia
2014-05-06 17:31 ` Ezequiel Garcia [this message]
2014-05-15  9:14   ` [PATCH v3 0/7] thermal: Armada 375/380 SoC support Zhang Rui

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=20140506173157.GA22929@arch.cereza \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=alior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --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