All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] arm64: dts: renesas: r8a779{7|8}0: add TMU support
Date: Thu, 13 Sep 2018 23:29:10 +0300	[thread overview]
Message-ID: <69147b26-1083-362f-5f7b-fcd274d900c2@cogentembedded.com> (raw)
In-Reply-To: <20180912093949.dbxaerbvpqzxdgnk@verge.net.au>

On 09/12/2018 12:39 PM, Simon Horman wrote:

>>>>>> Describe TMUs in the R8A779{7|8}0 device trees.
>>>>>>
>>>>>> Based on the original (and large) patches by Vladimir Barinov.
>>>>>>
>>>>>> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
>>>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>>>
>>>>>> ---
>>>>>> This patch is against the 'renesas-devel-20180906-v4.19-rc2' branch of
>>>>>> Simon Horman's 'renesas.git' repo plus the R8A779{7|8}0 DT patch adding
>>>>>> the CMT support).
>>>>>>
>>>>>> The R8A779{7|8}0 TMU DT binding update have been just posted...
>>>>>>
>>>>>>  arch/arm64/boot/dts/renesas/r8a77970.dtsi |   66 ++++++++++++++++++++++++++++++
>>>>>>  arch/arm64/boot/dts/renesas/r8a77980.dtsi |   66 ++++++++++++++++++++++++++++++
>>>>>>  2 files changed, 132 insertions(+)
>>>>>>
>>>>>> Index: renesas/arch/arm64/boot/dts/renesas/r8a77970.dtsi
>>>>>> ===================================================================
>>>>>> --- renesas.orig/arch/arm64/boot/dts/renesas/r8a77970.dtsi
>>>>>> +++ renesas/arch/arm64/boot/dts/renesas/r8a77970.dtsi
>>>>>> @@ -316,6 +316,72 @@
>>>>>>  			resets = <&cpg 407>;
>>>>>>  		};
>>>>>>  
>>>>>> +		tmu0: timer@e61e0000 {
>>>>>> +			compatible = "renesas,tmu-r8a77970", "renesas,tmu";
>>>>>> +			reg = <0 0xe61e0000 0 0x30>;
>>>>>> +			interrupts = <GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 137 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>;
>>>>>> +			clocks = <&cpg CPG_MOD 125>;
>>>>>> +			clock-names = "fck";
>>>>>> +			power-domains = <&sysc R8A77970_PD_ALWAYS_ON>;
>>>>>> +			resets = <&cpg 125>;
>>>>>> +			status = "disabled";
>>>>>> +		};
>>>>>> +
>>>>>> +		tmu1: timer@e6fc0000 {
>>>>>> +			compatible = "renesas,tmu-r8a77970", "renesas,tmu";
>>>>>> +			reg = <0 0xe6fc0000 0 0x30>;
>>>>>> +			interrupts = <GIC_SPI 128 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 129 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 130 IRQ_TYPE_LEVEL_HIGH>;
>>>>>> +			clocks = <&cpg CPG_MOD 124>;
>>>>>> +			clock-names = "fck";
>>>>>> +			power-domains = <&sysc R8A77970_PD_ALWAYS_ON>;
>>>>>> +			resets = <&cpg 124>;
>>>>>> +			status = "disabled";
>>>>>> +		};
>>>>>> +
>>>>>> +		tmu2: timer@e6fd0000 {
>>>>>> +			compatible = "renesas,tmu-r8a77970", "renesas,tmu";
>>>>>> +			reg = <0 0xe6fd0000 0 0x30>;
>>>>>> +			interrupts = <GIC_SPI 303 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 304 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 305 IRQ_TYPE_LEVEL_HIGH>;
>>>>>
>>>>> Should GIC_SPI 306 also be here for TMU 2 channel 3?> 
>>>>> And likewise for the r8a77980 (V3H)
>>>>
>>>>    There are only 3 channels per TMU according to the beginning of the TMU chapter.
>>>>
>>>>> The documentation seems inconsistent as I see this listed in the
>>>>> interrupt controller documentation. But I do not see that channel
>>>>> documented in the TMU documentation.
>>>>
>>>>    Right!
>>>>
>>>>>> +			clocks = <&cpg CPG_MOD 123>;
>>>>>> +			clock-names = "fck";
>>>>>> +			power-domains = <&sysc R8A77970_PD_ALWAYS_ON>;
>>>>>> +			resets = <&cpg 123>;
>>>>>> +			status = "disabled";
>>>>>> +		};
>>>>>> +
>>>>>> +		tmu3: timer@e6fe0000 {
>>>>>> +			compatible = "renesas,tmu-r8a7797", "renesas,tmu";
>>>>>> +			reg = <0 0xe6fe0000 0 0x30>;
>>>>>> +			interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 132 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
>>>>>> +			clocks = <&cpg CPG_MOD 122>;
>>>>>> +			clock-names = "fck";
>>>>>> +			power-domains = <&sysc R8A77970_PD_ALWAYS_ON>;
>>>>>> +			resets = <&cpg 122>;
>>>>>> +			status = "disabled";
>>>>>> +		};
>>>>>> +
>>>>>> +		tmu4: timer@ffc00000 {
>>>>>> +			compatible = "renesas,tmu-r8a7797", "renesas,tmu";
>>>>>> +			reg = <0 0xffc00000 0 0x30>;
>>>>>> +			interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 117 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH>,
>>>>>> +				     <GIC_SPI 369 IRQ_TYPE_LEVEL_HIGH>;
>>>>>
>>>>> Should GIC_SPI 369 for TMU 4 channel 3 be present not here for
>>>>> the r8a77970 (V3M) but rather below for the r8a77980 (V3H) ?
>>>>
>>>>    I don't think it should be pesent in either place, and I thought I had removed
>>>> the 4th IRQ from every node before posting... :-/
>>>>
>>>>> As per my note above, the documentation seems inconsistent here.
>>>>
>>>>    Yes.
>>>
>>> Lets go with no 4th IRQ anywhere :)
>>
>>    After having studied the manual, 4th IRQ might have sometging to do with the input capture channel capability which uses an extra IRQ output.
>>
>>> Could you send an updated patch?
>>
>>    Sure. I'll verify and repost.
> 
> Geert seems to want us to consider this further.

   Geert's main concern is about the different TMU hardware on the same SoC, like
the CMT types 0/1 (each described in its separate chapter). Somehow we don't have
the same situation with TMUs...

> As DT describes hardware it seems reasonable that we should describe the
> TMU device fully in DT, including all IRQs. But it seems to me that the
> documentation may not be consistent enough to judge how to do that.
> So perhaps a way forwards is to seek clarification of the documentation?

   Yes, definitely won't hurts. :-)

MBR, Sergei

  reply	other threads:[~2018-09-13 20:29 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 18:48 [PATCH v2 0/2] Add R8A77980/Condor PCIe support Sergei Shtylyov
2018-08-27 18:48 ` Sergei Shtylyov
2018-08-27 18:48 ` Sergei Shtylyov
2018-08-27 18:52 ` Sergei Shtylyov
2018-08-27 18:52   ` Sergei Shtylyov
2018-08-27 18:52   ` Sergei Shtylyov
2018-08-27 18:53 ` [PATCH v3 1/2] arm64: dts: renesas: r8a77980: add " Sergei Shtylyov
2018-08-27 18:53   ` Sergei Shtylyov
2018-08-27 18:53   ` Sergei Shtylyov
2018-08-30 12:32   ` Simon Horman
2018-08-30 12:32     ` Simon Horman
2018-08-30 12:32     ` Simon Horman
2018-08-27 18:54 ` [PATCH v3 2/2] arm64: dts: renesas: condor: " Sergei Shtylyov
2018-08-27 18:54   ` Sergei Shtylyov
2018-08-27 18:54   ` Sergei Shtylyov
2018-08-30 12:32   ` Simon Horman
2018-08-30 12:32     ` Simon Horman
2018-08-30 12:32     ` Simon Horman
2018-09-06 17:02 ` [PATCH] arm64: dts: renesas: r8a779{7|8}0: add CMT support Sergei Shtylyov
2018-09-06 18:43   ` Sergei Shtylyov
2018-09-07 18:58 ` [PATCH v2] " Sergei Shtylyov
2018-09-10  9:05   ` Simon Horman
2018-09-19  7:47   ` Geert Uytterhoeven
2018-09-19  9:19     ` Simon Horman
2018-09-07 20:14 ` [PATCH] arm64: dts: renesas: r8a779{7|8}0: add TMU support Sergei Shtylyov
2018-09-10  9:23   ` Simon Horman
2018-09-10 12:04     ` Sergei Shtylyov
2018-09-11 13:36       ` Simon Horman
2018-09-11 14:12         ` Geert Uytterhoeven
2018-09-11 18:35         ` Sergei Shtylyov
2018-09-12  9:39           ` Simon Horman
2018-09-13 20:29             ` Sergei Shtylyov [this message]
2018-09-13 20:14           ` Sergei Shtylyov
2018-09-19 20:02 ` [PATCH] arm64: dts: renesas: r8a779{7|8}0: add TPU support Sergei Shtylyov
2018-09-19 20:21   ` Sergei Shtylyov
2018-09-21  7:35     ` Simon Horman
2018-09-21  8:27       ` Sergei Shtylyov
2018-09-22 20:30 ` [PATCH v2] " Sergei Shtylyov
2018-09-24  9:07   ` Simon Horman
2018-09-24 14:44     ` Sergei Shtylyov
2018-09-24 15:32       ` Simon Horman
2018-09-24 11:29   ` Geert Uytterhoeven
2018-09-24 17:55     ` Sergei Shtylyov
2018-09-24 18:33 ` [PATCH v3] " Sergei Shtylyov
2018-09-24 19:36   ` Geert Uytterhoeven
2018-09-25  7:42     ` Simon Horman
2018-09-24 20:13 ` [PATCH v2] arm64: dts: renesas: r8a779{7|8}0: add TMU support Sergei Shtylyov
2018-10-18 18:32   ` Sergei Shtylyov
2018-10-19 13:43     ` Simon Horman
2018-10-01 20:25 ` [PATCH] arm64: dts: renesas: r8a779{7|8}0: add PWM support Sergei Shtylyov
2018-10-02  7:16   ` Geert Uytterhoeven
2018-10-04  9:33     ` Simon Horman
2018-10-05 19:25 ` [PATCH] arm64: dts: renesas: r8a77970: add thermal support Sergei Shtylyov
2018-10-05 19:33   ` Sergei Shtylyov
2018-10-08  7:55   ` Simon Horman
2018-10-08  8:12   ` Geert Uytterhoeven
2018-10-08 16:35     ` Sergei Shtylyov
2018-10-08 16:40       ` Geert Uytterhoeven
2018-10-08 18:04         ` Sergei Shtylyov
2018-10-10  7:10           ` Geert Uytterhoeven
2018-10-09 19:37 ` [PATCH] arm64: dts: renesas: r8a77980: " Sergei Shtylyov
2018-10-10  8:36   ` Simon Horman
2018-10-10 10:47     ` Sergei Shtylyov
2018-10-10 10:52       ` Niklas Söderlund
2018-10-10 10:57   ` Niklas Söderlund
2018-10-10 11:20     ` Sergei Shtylyov
2018-10-09 19:47 ` [PATCH v2] arm64: dts: renesas: r8a77970: " Sergei Shtylyov
2018-10-10  7:12   ` Geert Uytterhoeven
2018-10-12 11:21     ` Simon Horman
2018-10-12 14:36       ` Sergei Shtylyov
2018-10-15 15:43         ` Simon Horman
2018-10-10 19:18 ` [PATCH v2] arm64: dts: renesas: r8a77980: " Sergei Shtylyov
2018-10-10 22:11   ` Niklas Söderlund
2018-10-11  7:02     ` Geert Uytterhoeven
2018-10-11  7:30       ` Niklas Söderlund
2018-10-12 11:23         ` Simon Horman
2018-10-16 19:36 ` [PATCH] arm64: dts: renesas: r8a779{7|8}0: add MSIOF support Sergei Shtylyov
2018-10-17  8:12   ` Simon Horman
2018-10-17  8:52     ` Geert Uytterhoeven
2018-10-18 12:45       ` Simon Horman
2018-10-18 16:48 ` [PATCH] arm64: dts: renesas: condor: switch from EtherAVB to GEther Sergei Shtylyov
2018-10-31 14:30   ` Simon Horman
2018-10-31 17:29     ` Sergei Shtylyov
2018-11-02 11:25       ` Simon Horman
2018-10-19 19:10 ` [PATCH v2] arm64: dts: renesas: r8a779{7|8}0: add MSIOF support Sergei Shtylyov
2018-10-29 10:24   ` Simon Horman

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=69147b26-1083-362f-5f7b-fcd274d900c2@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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.