mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	<grygorii.strashko@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3*: Introduce reg definition for interrupt routers
Date: Tue, 11 May 2021 21:53:42 +0530	[thread overview]
Message-ID: <45c92c1d-1d58-4711-ac07-68406492b86b@ti.com> (raw)
In-Reply-To: <20210510145508.8994-1-nm@ti.com>



On 10/05/21 8:25 pm, Nishanth Menon wrote:
> Interrupt routers are memory mapped peripherals, that are organized
> in our dts bus hierarchy to closely represents the actual hardware
> behavior.
> 
> However, without explicitly calling out the reg property, using
> 2021.03+ dt-schema package, this exposes the following problem with
> dtbs_check:
> 
> /arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml: bus@100000:
> interrupt-controller0: {'type': 'object'} is not allowed for
> {'compatible': ['ti,sci-intr'], .....
> 
> Even though we don't use interrupt router directly via memory mapped
> registers and have to use it via the system controller, the hardware
> block is memory mapped, so describe the base address in device tree.
> 
> This is a valid, comprehensive description of hardware and permitted
> by the existing ti,sci-intr schema.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> 
> if possible, I'd like to pick this fixup for 5.13 window..
> 
>  arch/arm64/boot/dts/ti/k3-am64-main.dtsi        | 3 ++-
>  arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi         | 3 ++-
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi        | 6 ++++--
>  arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi      | 3 ++-
>  arch/arm64/boot/dts/ti/k3-j7200-main.dtsi       | 6 ++++--
>  arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 3 ++-
>  arch/arm64/boot/dts/ti/k3-j721e-main.dtsi       | 6 ++++--
>  arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 3 ++-
>  8 files changed, 22 insertions(+), 11 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> index b2bcbf23eefd..a49e41021573 100644
> --- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> @@ -373,8 +373,9 @@ main_spi4: spi@20140000 {
>  		clocks = <&k3_clks 145 0>;
>  	};
>  
> -	main_gpio_intr: interrupt-controller0 {
> +	main_gpio_intr: interrupt-controller@a00000 {
>  		compatible = "ti,sci-intr";
> +		reg = <0x00 0xa00000 0x00 0x800>;

IIRC, we are going with 0x00a00000 (0x%8x) for all regs. With that fixed for all
regs:

Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>

Thanks and regards,
Lokesh

  parent reply	other threads:[~2021-05-11 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 14:55 Nishanth Menon
2021-05-11  7:13 ` Tero Kristo
2021-05-11 16:23 ` Lokesh Vutla [this message]
2021-05-11 19:56   ` Nishanth Menon

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=45c92c1d-1d58-4711-ac07-68406492b86b@ti.com \
    --to=lokeshvutla@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®