All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 3/4] arm64: dts: marvell: add macro to make distinction between node names
Date: Fri, 21 Sep 2018 16:15:27 +0200	[thread overview]
Message-ID: <87fty3gcn4.fsf@bootlin.com> (raw)
In-Reply-To: <20180830081501.11569-3-miquel.raynal@bootlin.com> (Miquel Raynal's message of "Thu, 30 Aug 2018 10:15:00 +0200")

Hi Miquel,
 
 On jeu., ao?t 30 2018, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> Because the label is different between CPs, the full path of a node is
> unique. However, when referring to the end of the path only (the node
> name), this name is not unique anymore.
>
> The *thermal_zone_of_sensor_register() functions of the thermal core
> present this limitation and prevent having a thermal-zone per CP.
>
> Add a macro to make the distinction between node names to solve this
> situation.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

Applied on mvebu/dt64

Thanks,

Gregory

> ---
>  arch/arm64/boot/dts/marvell/armada-common.dtsi | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-common.dtsi b/arch/arm64/boot/dts/marvell/armada-common.dtsi
> index d5e8aedec188..b29c6405d214 100644
> --- a/arch/arm64/boot/dts/marvell/armada-common.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-common.dtsi
> @@ -7,4 +7,5 @@
>  #define PASTER(x, y) x ## y
>  #define EVALUATOR(x, y) PASTER(x, y)
>  #define CP110_LABEL(name) EVALUATOR(CP110_NAME, EVALUATOR(_, name))
> +#define CP110_NODE_NAME(name) EVALUATOR(CP110_NAME, EVALUATOR(-, name))
>  #define ADDRESSIFY(addr) EVALUATOR(0x, addr)
> -- 
> 2.17.1
>

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	devicetree@vger.kernel.org,
	Antoine Tenart <antoine.tenart@bootlin.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Rob Herring <robh+dt@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [RESEND PATCH 3/4] arm64: dts: marvell: add macro to make distinction between node names
Date: Fri, 21 Sep 2018 16:15:27 +0200	[thread overview]
Message-ID: <87fty3gcn4.fsf@bootlin.com> (raw)
In-Reply-To: <20180830081501.11569-3-miquel.raynal@bootlin.com> (Miquel Raynal's message of "Thu, 30 Aug 2018 10:15:00 +0200")

Hi Miquel,
 
 On jeu., août 30 2018, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> Because the label is different between CPs, the full path of a node is
> unique. However, when referring to the end of the path only (the node
> name), this name is not unique anymore.
>
> The *thermal_zone_of_sensor_register() functions of the thermal core
> present this limitation and prevent having a thermal-zone per CP.
>
> Add a macro to make the distinction between node names to solve this
> situation.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

Applied on mvebu/dt64

Thanks,

Gregory

> ---
>  arch/arm64/boot/dts/marvell/armada-common.dtsi | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-common.dtsi b/arch/arm64/boot/dts/marvell/armada-common.dtsi
> index d5e8aedec188..b29c6405d214 100644
> --- a/arch/arm64/boot/dts/marvell/armada-common.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-common.dtsi
> @@ -7,4 +7,5 @@
>  #define PASTER(x, y) x ## y
>  #define EVALUATOR(x, y) PASTER(x, y)
>  #define CP110_LABEL(name) EVALUATOR(CP110_NAME, EVALUATOR(_, name))
> +#define CP110_NODE_NAME(name) EVALUATOR(CP110_NAME, EVALUATOR(-, name))
>  #define ADDRESSIFY(addr) EVALUATOR(0x, addr)
> -- 
> 2.17.1
>

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-09-21 14:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  8:14 [RESEND PATCH 1/4] arm64: dts: marvell: move AP806/CP110 thermal nodes into a new syscon Miquel Raynal
2018-08-30  8:14 ` Miquel Raynal
2018-08-30  8:14 ` [RESEND PATCH 2/4] arm64: dts: marvell: add thermal-zone node in ap806 DTSI file Miquel Raynal
2018-08-30  8:14   ` Miquel Raynal
2018-09-21 14:15   ` Gregory CLEMENT
2018-09-21 14:15     ` Gregory CLEMENT
2018-08-30  8:15 ` [RESEND PATCH 3/4] arm64: dts: marvell: add macro to make distinction between node names Miquel Raynal
2018-08-30  8:15   ` Miquel Raynal
2018-09-21 14:15   ` Gregory CLEMENT [this message]
2018-09-21 14:15     ` Gregory CLEMENT
2018-08-30  8:15 ` [RESEND PATCH 4/4] arm64: dts: marvell: add thermal-zone node in cp110 DTSI file Miquel Raynal
2018-08-30  8:15   ` Miquel Raynal
2018-09-21 14:15   ` Gregory CLEMENT
2018-09-21 14:15     ` Gregory CLEMENT
2018-09-21 14:14 ` [RESEND PATCH 1/4] arm64: dts: marvell: move AP806/CP110 thermal nodes into a new syscon Gregory CLEMENT
2018-09-21 14:14   ` Gregory CLEMENT

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=87fty3gcn4.fsf@bootlin.com \
    --to=gregory.clement@bootlin.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 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.