From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
Zhang Rui <rui.zhang@intel.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux-pm@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] thermal: armada: Remove support for A375-Z1 SoC
Date: Fri, 7 Nov 2014 23:27:36 +0100 [thread overview]
Message-ID: <20141107232736.456b1b79@free-electrons.com> (raw)
In-Reply-To: <545CBDEF.6050502@free-electrons.com>
Dear Ezequiel Garcia,
On Fri, 07 Nov 2014 09:41:19 -0300, Ezequiel Garcia wrote:
> We can do that if you think it's really useful. However, I think we've
> designed this so *nobody* would actually have to put the z1 compatible
> string. The mvebu quirk (tries) to auto-detect it from the revision
> register and hot fix the compatible string.
Correct.
> Moreover, I'm not at all sure *anyone* would have a Z1 board except
> early developers like us. Am I being too naive here?
I confirm: those early revisions have only been provided to a very
small selection of persons, mainly within Marvell, and only a few
external partners which are all well aware of the early status of such
SoC revisions.
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 1/2] thermal: armada: Remove support for A375-Z1 SoC
Date: Fri, 7 Nov 2014 23:27:36 +0100 [thread overview]
Message-ID: <20141107232736.456b1b79@free-electrons.com> (raw)
In-Reply-To: <545CBDEF.6050502@free-electrons.com>
Dear Ezequiel Garcia,
On Fri, 07 Nov 2014 09:41:19 -0300, Ezequiel Garcia wrote:
> We can do that if you think it's really useful. However, I think we've
> designed this so *nobody* would actually have to put the z1 compatible
> string. The mvebu quirk (tries) to auto-detect it from the revision
> register and hot fix the compatible string.
Correct.
> Moreover, I'm not at all sure *anyone* would have a Z1 board except
> early developers like us. Am I being too naive here?
I confirm: those early revisions have only been provided to a very
small selection of persons, mainly within Marvell, and only a few
external partners which are all well aware of the early status of such
SoC revisions.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-07 22:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:00 [PATCH 0/2] Farewell Armada 375 Z1 support Ezequiel Garcia
2014-11-04 16:00 ` Ezequiel Garcia
2014-11-04 16:00 ` [PATCH 1/2] thermal: armada: Remove support for A375-Z1 SoC Ezequiel Garcia
2014-11-04 16:00 ` Ezequiel Garcia
2014-11-07 3:26 ` Jason Cooper
2014-11-07 3:26 ` Jason Cooper
2014-11-07 12:41 ` Ezequiel Garcia
2014-11-07 12:41 ` Ezequiel Garcia
2014-11-07 12:59 ` Jason Cooper
2014-11-07 12:59 ` Jason Cooper
2014-11-07 22:27 ` Thomas Petazzoni [this message]
2014-11-07 22:27 ` Thomas Petazzoni
2014-11-09 3:16 ` Jason Cooper
2014-11-09 3:16 ` Jason Cooper
2014-11-20 19:38 ` Eduardo Valentin
2014-11-20 19:38 ` Eduardo Valentin
2014-11-21 20:18 ` Jason Cooper
2014-11-21 20:18 ` Jason Cooper
2014-11-21 21:51 ` Thomas Petazzoni
2014-11-21 21:51 ` Thomas Petazzoni
2014-11-21 22:05 ` Jason Cooper
2014-11-21 22:05 ` Jason Cooper
2014-11-21 22:31 ` Thomas Petazzoni
2014-11-21 22:31 ` Thomas Petazzoni
2014-11-04 16:00 ` [PATCH 2/2] ARM: mvebu: Remove thermal quirk for A375 Z1 revision Ezequiel Garcia
2014-11-04 16:00 ` Ezequiel Garcia
2014-11-09 3:38 ` Jason Cooper
2014-11-09 3:38 ` Jason Cooper
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=20141107232736.456b1b79@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.hesselbarth@gmail.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.