From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
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 17:59:05 +0200 [thread overview]
Message-ID: <534EA8C9.7010907@gmail.com> (raw)
In-Reply-To: <1397657720-10893-6-git-send-email-ezequiel.garcia@free-electrons.com>
On 04/16/2014 04:15 PM, Ezequiel Garcia wrote:
> The initial release of the Armada 375 DB board has an Armada 375
> Z1 stepping silicon. This commit introduces a quirk that allows
> to workaround a series of issues with the thermal sensor in this
> stepping, but updating the devicetree:
>
> * Updates the compatible string for the thermal, so the driver
> can perform a specific initialization of the sensor.
>
> * Moves the offset of the thermal control register. This quirk
> allows to specifiy the correct (A0 stepping) offset in the
> devicetree.
>
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---
> arch/arm/mach-mvebu/board-v7.c | 57 ++++++++++++++++++++++++++++++++++++++
> arch/arm/mach-mvebu/mvebu-soc-id.h | 3 ++
> 2 files changed, 60 insertions(+)
>
> diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
> index 333fca8..93f50f2 100644
> --- a/arch/arm/mach-mvebu/board-v7.c
> +++ b/arch/arm/mach-mvebu/board-v7.c
> @@ -96,10 +96,66 @@ static void __init i2c_quirk(void)
> return;
> }
>
> +#define A375_Z1_THERMAL_FIXUP_OFFSET 0xc
> +
> +static void __init thermal_quirk(void)
Are we sure, we want to fixup quirks like this the way below?
Alternatively, we can also keep some armada-375-z1.dtsi and one
for the board including it.
Sebastian
> +{
> + struct device_node *np;
> + u32 dev, rev;
> +
> + if (mvebu_get_soc_id(&dev, &rev) && rev > ARMADA_375_Z1_REV)
> + return;
> +
> + for_each_compatible_node(np, NULL, "marvell,armada375-thermal") {
> + struct property *prop;
> + __be32 newval, *newprop, *oldprop;
> + int len;
> +
> + /*
> + * The register offset is at a wrong location. This quirk
> + * creates a new reg property as a clone of the previous
> + * one and corrects the offset.
> + */
> + oldprop = (__be32 *)of_get_property(np, "reg", &len);
> + if (!oldprop)
> + continue;
> +
> + /* Create a duplicate of the 'reg' property */
> + prop = kzalloc(sizeof(*prop), GFP_KERNEL);
> + prop->length = len;
> + prop->name = kstrdup("reg", GFP_KERNEL);
> + prop->value = kzalloc(len, GFP_KERNEL);
> + memcpy(prop->value, oldprop, len);
> +
> + /* Fixup the register offset of the second entry */
> + oldprop += 2;
> + newprop = (__be32 *)prop->value + 2;
> + newval = cpu_to_be32(be32_to_cpu(*oldprop) -
> + A375_Z1_THERMAL_FIXUP_OFFSET);
> + *newprop = newval;
> + of_update_property(np, prop);
> +
> + /*
> + * The thermal controller needs some quirk too, so let's change
> + * the compatible string to reflect this.
> + */
> + prop = kzalloc(sizeof(*prop), GFP_KERNEL);
> + prop->name = kstrdup("compatible", GFP_KERNEL);
> + prop->length = sizeof("marvell,armada375-z1-thermal");
> + prop->value = kstrdup("marvell,armada375-z1-thermal",
> + GFP_KERNEL);
> + of_update_property(np, prop);
> + }
> + return;
> +}
> +
> static void __init mvebu_dt_init(void)
> {
> if (of_machine_is_compatible("plathome,openblocks-ax3-4"))
> i2c_quirk();
> + if (of_machine_is_compatible("marvell,a375-db"))
> + thermal_quirk();
> +
> of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> }
>
> @@ -123,6 +179,7 @@ static const char * const armada_375_dt_compat[] = {
>
> DT_MACHINE_START(ARMADA_375_DT, "Marvell Armada 375 (Device Tree)")
> .init_time = mvebu_timer_and_clk_init,
> + .init_machine = mvebu_dt_init,
> .restart = mvebu_restart,
> .dt_compat = armada_375_dt_compat,
> MACHINE_END
> diff --git a/arch/arm/mach-mvebu/mvebu-soc-id.h b/arch/arm/mach-mvebu/mvebu-soc-id.h
> index 3165425..294a443 100644
> --- a/arch/arm/mach-mvebu/mvebu-soc-id.h
> +++ b/arch/arm/mach-mvebu/mvebu-soc-id.h
> @@ -20,6 +20,9 @@
> #define MV78XX0_A0_REV 0x1
> #define MV78XX0_B0_REV 0x2
>
> +/* Armada 375 */
> +#define ARMADA_375_Z1_REV 0x0
> +
> #ifdef CONFIG_ARCH_MVEBU
> int mvebu_get_soc_id(u32 *dev, u32 *rev);
> #else
>
next prev parent reply other threads:[~2014-04-16 15:59 UTC|newest]
Thread overview: 19+ 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 ` [PATCH 1/6] thermal: armada: Rename armada_thermal_ops struct 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 ` [PATCH 3/6] thermal: armada: Add generic infrastructure to handle the sensor Ezequiel Garcia
2014-04-16 14:15 ` [PATCH 4/6] thermal: armada: Support Armada 375 SoC Ezequiel Garcia
2014-04-16 15:38 ` Jason Cooper
2014-04-16 15:49 ` Ezequiel Garcia
2014-04-16 16:40 ` Jason Cooper
2014-04-16 15:44 ` Jason Cooper
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 15:59 ` Sebastian Hesselbarth [this message]
2014-04-16 16:03 ` Thomas Petazzoni
2014-04-16 16:08 ` Andrew Lunn
2014-04-16 16:19 ` Thomas Petazzoni
2014-04-16 16:34 ` Andrew Lunn
2014-04-16 16:55 ` Jason Cooper
2014-04-16 17:08 ` Thomas Petazzoni
2014-04-16 14:15 ` [PATCH 6/6] ARM: mvebu: Enable the thermal sensor in Armada 375 SoC 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=534EA8C9.7010907@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).