From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Zhang Rui <rui.zhang@intel.com>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org,
Gregory Clement <gregory.clement@free-electrons.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>
Subject: Re: [PATCH 5/6] ARM: mvebu: Add thermal quirk for the Armada 375 DB board
Date: Wed, 16 Apr 2014 19:08:54 +0200 [thread overview]
Message-ID: <20140416190854.52e2a4bb@skate> (raw)
In-Reply-To: <20140416165548.GI28159@titan.lakedaemon.net>
Dear Jason Cooper,
On Wed, 16 Apr 2014 12:55:48 -0400, Jason Cooper wrote:
> > Sounds like a good plan. Try to keep all the mess to support Z1 in one
> > place so that it can be easily taken out once people have A0.
>
> Agreed. Thomas, do you think you'll be able to get a definitive answer
> from Marvell re the number of Z1 boards in the wild? Once they've moved
> to the A0, of course.
My understanding is that Marvell has never been interested in having
mainline support for the Z1 stepping. It just happens to be a necessary
step to make progress with the general goal of supporting 375 in
mainline, but I don't expect Marvell to be interested in supporting the
Z1 boards in the wild.
> Unless we can get a hard answer on that, I doubt we'll ever withdraw
> support for the Z1. Not that that's a bad thing, just trying to be
> realistic. If we add code, expect to support it.
Yes, indeed.
> And keeping it all in one place is kind of an impossibility. Just for
> thermal Z1, there are changes to the binding docs, the thermal driver,
> and the soc code.
>
> I'd say it's more important to keep it clean, with dts files targeting
> the A0+ SoCs, and the Z1 being the exception case(s).
That's what we've tried to do so far: the thermal driver works for the
A0+ by default, and only as an exception supports Z1.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: mvebu: Add thermal quirk for the Armada 375 DB board
Date: Wed, 16 Apr 2014 19:08:54 +0200 [thread overview]
Message-ID: <20140416190854.52e2a4bb@skate> (raw)
In-Reply-To: <20140416165548.GI28159@titan.lakedaemon.net>
Dear Jason Cooper,
On Wed, 16 Apr 2014 12:55:48 -0400, Jason Cooper wrote:
> > Sounds like a good plan. Try to keep all the mess to support Z1 in one
> > place so that it can be easily taken out once people have A0.
>
> Agreed. Thomas, do you think you'll be able to get a definitive answer
> from Marvell re the number of Z1 boards in the wild? Once they've moved
> to the A0, of course.
My understanding is that Marvell has never been interested in having
mainline support for the Z1 stepping. It just happens to be a necessary
step to make progress with the general goal of supporting 375 in
mainline, but I don't expect Marvell to be interested in supporting the
Z1 boards in the wild.
> Unless we can get a hard answer on that, I doubt we'll ever withdraw
> support for the Z1. Not that that's a bad thing, just trying to be
> realistic. If we add code, expect to support it.
Yes, indeed.
> And keeping it all in one place is kind of an impossibility. Just for
> thermal Z1, there are changes to the binding docs, the thermal driver,
> and the soc code.
>
> I'd say it's more important to keep it clean, with dts files targeting
> the A0+ SoCs, and the Z1 being the exception case(s).
That's what we've tried to do so far: the thermal driver works for the
A0+ by default, and only as an exception supports Z1.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-16 17:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:15 [PATCH 0/6] thermal: Add Armada 375 SoC support Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 1/6] thermal: armada: Rename armada_thermal_ops struct Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 2/6] thermal: armada: Add infrastructure to support generic formulas Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 3/6] thermal: armada: Add generic infrastructure to handle the sensor Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 4/6] thermal: armada: Support Armada 375 SoC Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 15:38 ` Jason Cooper
2014-04-16 15:38 ` Jason Cooper
2014-04-16 15:49 ` Ezequiel Garcia
2014-04-16 15:49 ` Ezequiel Garcia
2014-04-16 16:40 ` Jason Cooper
2014-04-16 16:40 ` Jason Cooper
2014-04-16 15:44 ` Jason Cooper
2014-04-16 15:44 ` Jason Cooper
2014-04-16 15:53 ` Ezequiel Garcia
2014-04-16 15:53 ` Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 5/6] ARM: mvebu: Add thermal quirk for the Armada 375 DB board Ezequiel Garcia
2014-04-16 14:15 ` Ezequiel Garcia
2014-04-16 15:59 ` Sebastian Hesselbarth
2014-04-16 15:59 ` Sebastian Hesselbarth
2014-04-16 16:03 ` Thomas Petazzoni
2014-04-16 16:03 ` Thomas Petazzoni
2014-04-16 16:08 ` Andrew Lunn
2014-04-16 16:08 ` Andrew Lunn
2014-04-16 16:19 ` Thomas Petazzoni
2014-04-16 16:19 ` Thomas Petazzoni
2014-04-16 16:34 ` Andrew Lunn
2014-04-16 16:34 ` Andrew Lunn
2014-04-16 16:55 ` Jason Cooper
2014-04-16 16:55 ` Jason Cooper
2014-04-16 17:08 ` Thomas Petazzoni [this message]
2014-04-16 17:08 ` Thomas Petazzoni
[not found] ` <1397657720-10893-1-git-send-email-ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-16 14:15 ` [PATCH 6/6] ARM: mvebu: Enable the thermal sensor in Armada 375 SoC Ezequiel Garcia
2014-04-16 14:15 ` 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=20140416190854.52e2a4bb@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.