From: Eduardo Valentin <edubezval@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Zhang Rui <rui.zhang@intel.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] thermal: rcar: Add binding docs for new R-Car Gen2 SoCs
Date: Sat, 6 Sep 2014 12:13:59 -0400 [thread overview]
Message-ID: <20140906161357.GA3573@developer> (raw)
In-Reply-To: <1409213552-5713-1-git-send-email-geert+renesas@glider.be>
Hello Geert,
On Thu, Aug 28, 2014 at 10:12:32AM +0200, Geert Uytterhoeven wrote:
> - r8a7792 (R-Car V2H)
> - r8a7793 (R-Car M2-N)
> - r8a7794 (R-Car E2)
>
> r8a7791 is now called "R-Car M2-W".
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I don't have any concerns on this patch and will be adding to my next
branch. But before that, I have one simple question. Although the
binding description mention about soc types, the rcar thermal driver do
not differentiate soc types, only supports the "renesas,rcar-thermal"
compatible.
Do you care explaining why we need the soc specific compatibles?
> ---
> v2: Drop RFC
> ---
> Documentation/devicetree/bindings/thermal/rcar-thermal.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/rcar-thermal.txt b/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> index 0ef00be44b01..43404b197933 100644
> --- a/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> @@ -7,7 +7,10 @@ Required properties:
> - "renesas,thermal-r8a73a4" (R-Mobile AP6)
> - "renesas,thermal-r8a7779" (R-Car H1)
> - "renesas,thermal-r8a7790" (R-Car H2)
> - - "renesas,thermal-r8a7791" (R-Car M2)
> + - "renesas,thermal-r8a7791" (R-Car M2-W)
> + - "renesas,thermal-r8a7792" (R-Car V2H)
> + - "renesas,thermal-r8a7793" (R-Car M2-N)
> + - "renesas,thermal-r8a7794" (R-Car E2)
> - reg : Address range of the thermal registers.
> The 1st reg will be recognized as common register
> if it has "interrupts".
> --
> 1.9.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Valentin <edubezval@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Zhang Rui <rui.zhang@intel.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] thermal: rcar: Add binding docs for new R-Car Gen2 SoCs
Date: Sat, 06 Sep 2014 16:13:59 +0000 [thread overview]
Message-ID: <20140906161357.GA3573@developer> (raw)
In-Reply-To: <1409213552-5713-1-git-send-email-geert+renesas@glider.be>
Hello Geert,
On Thu, Aug 28, 2014 at 10:12:32AM +0200, Geert Uytterhoeven wrote:
> - r8a7792 (R-Car V2H)
> - r8a7793 (R-Car M2-N)
> - r8a7794 (R-Car E2)
>
> r8a7791 is now called "R-Car M2-W".
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I don't have any concerns on this patch and will be adding to my next
branch. But before that, I have one simple question. Although the
binding description mention about soc types, the rcar thermal driver do
not differentiate soc types, only supports the "renesas,rcar-thermal"
compatible.
Do you care explaining why we need the soc specific compatibles?
> ---
> v2: Drop RFC
> ---
> Documentation/devicetree/bindings/thermal/rcar-thermal.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/thermal/rcar-thermal.txt b/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> index 0ef00be44b01..43404b197933 100644
> --- a/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> +++ b/Documentation/devicetree/bindings/thermal/rcar-thermal.txt
> @@ -7,7 +7,10 @@ Required properties:
> - "renesas,thermal-r8a73a4" (R-Mobile AP6)
> - "renesas,thermal-r8a7779" (R-Car H1)
> - "renesas,thermal-r8a7790" (R-Car H2)
> - - "renesas,thermal-r8a7791" (R-Car M2)
> + - "renesas,thermal-r8a7791" (R-Car M2-W)
> + - "renesas,thermal-r8a7792" (R-Car V2H)
> + - "renesas,thermal-r8a7793" (R-Car M2-N)
> + - "renesas,thermal-r8a7794" (R-Car E2)
> - reg : Address range of the thermal registers.
> The 1st reg will be recognized as common register
> if it has "interrupts".
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-09-06 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 8:12 [PATCH v2] thermal: rcar: Add binding docs for new R-Car Gen2 SoCs Geert Uytterhoeven
2014-08-28 8:12 ` Geert Uytterhoeven
2014-09-06 16:13 ` Eduardo Valentin [this message]
2014-09-06 16:13 ` Eduardo Valentin
2014-09-06 18:10 ` Geert Uytterhoeven
2014-09-06 18:10 ` Geert Uytterhoeven
2014-09-08 10:48 ` Eduardo Valentin
2014-09-08 10:48 ` Eduardo Valentin
2014-09-08 11:02 ` Geert Uytterhoeven
2014-09-08 11:02 ` Geert Uytterhoeven
2014-09-09 14:51 ` Eduardo Valentin
2014-09-09 14:51 ` Eduardo Valentin
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=20140906161357.GA3573@developer \
--to=edubezval@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rui.zhang@intel.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.