All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@collabora.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Hari Nagalla <hnagalla@ti.com>,
	kernel@collabora.com, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs
Date: Fri, 24 Mar 2023 12:01:19 +0000	[thread overview]
Message-ID: <659687a489b4baea1f2cbb879fc59037b39f7ea0.camel@collabora.com> (raw)
In-Reply-To: <20230308205833.GA1768401@p14s>

On Wed, 2023-03-08 at 13:58 -0700, Mathieu Poirier wrote:
> On Thu, Mar 02, 2023 at 05:14:48PM +0000, Martyn Welch wrote:
> 
> > +examples:
> > +  - |
> > +    reserved-memory {
> > +        #address-cells = <2>;
> > +        #size-cells = <2>;
> > +
> > +        mcu_m4fss_dma_memory_region: m4f-dma-memory@9cb00000 {
> > +            compatible = "shared-dma-pool";
> > +            reg = <0x00 0x9cb00000 0x00 0x100000>;
> > +            no-map;
> > +        };
> > +
> > +        mcu_m4fss_memory_region: m4f-memory@9cc00000 {
> > +            compatible = "shared-dma-pool";
> > +            reg = <0x00 0x9cc00000 0x00 0xe00000>;
> > +            no-map;
> > +        };
> > +    };
> > +
> > +    soc {
> > +        #address-cells = <2>;
> > +        #size-cells = <2>;
> > +
> > +        mailbox0_cluster0: mailbox-0 {
> > +            #mbox-cells = <1>;
> > +
> > +            mbox_m4_0: mbox-m4-0 {
> > +                ti,mbox-rx = <0 0 0>;
> > +                ti,mbox-tx = <1 0 0>;
> > +            };
> > +        };
> > +
> > +        bus@f0000 {
> > +            compatible = "simple-bus";
> > +            #address-cells = <2>;
> > +            #size-cells = <2>;
> > +            ranges = <0x00 0x04000000 0x00 0x04000000 0x00
> > 0x01ff1400>;
> > +
> > +            bus@4000000 {
> > +                compatible = "simple-bus";
> > +                #address-cells = <2>;
> > +                #size-cells = <2>;
> > +                ranges = <0x00 0x04000000 0x00 0x04000000 0x00
> > 0x01ff1400>;
> > +
> > +                mcu_m4fss: m4fss@5000000 {
> > +                    compatible = "ti,am64-m4fss";
> > +                    reg = <0x00 0x5000000 0x00 0x30000>,
> > +                          <0x00 0x5040000 0x00 0x10000>;
> > +                    reg-names = "iram", "dram";
> > +                    ti,sci = <&dmsc>;
> > +                    ti,sci-dev-id = <9>;
> > +                    ti,sci-proc-ids = <0x18 0xff>;
> > +                    resets = <&k3_reset 9 1>;
> > +                    firmware-name = "am62-mcu-m4f0_0-fw";
> > +                    mboxes = <&mailbox0_cluster0 &mbox_m4_0>;
> 
> This doesn't look right since mbox_m4_0 is defined within
> mailbox0_cluster0.
> 

Looking at other users of the omap mailboxes (and not wanting to spend
ages trawling back through the mailing list archives to try and work
out why it's specified the way it is) it seems that this is the way
that these mailboxes are specified.

For instance in `arch/arm/boot/dts/omap4-l4.dtsi`, the mailbox is
defined:

                mailbox: mailbox@0 {
                        compatible = "ti,omap4-mailbox";
                        reg = <0x0 0x200>;
                        interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
                        #mbox-cells = <1>;
                        ti,mbox-num-users = <3>;
                        ti,mbox-num-fifos = <8>;
                        mbox_ipu: mbox-ipu {
                                ti,mbox-tx = <0 0 0>;
                                ti,mbox-rx = <1 0 0>;
                        };
                        mbox_dsp: mbox-dsp {
                                ti,mbox-tx = <3 0 0>;
                                ti,mbox-rx = <2 0 0>;
                        };
                };

It's users in `arch/arm/boot/dts/omap4.dtsi`:

                dsp: dsp {
                        ...
                        mboxes = <&mailbox &mbox_dsp>;
                        ...
                };

                ipu: ipu@55020000 {
                        ...
                        mboxes = <&mailbox &mbox_ipu>;
                        ...
                };


> > +                    memory-region =
> > <&mcu_m4fss_dma_memory_region>,
> > +                                    <&mcu_m4fss_memory_region>;
> > +                };
> > +            };
> > +        };
> > +    };
> > -- 
> > 2.39.1
> > 


  parent reply	other threads:[~2023-03-24 12:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 17:14 [PATCH v3 0/3] TI K3 M4F support on AM64x and AM62x SoCs Martyn Welch
2023-03-02 17:14 ` [PATCH v3 1/3] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs Martyn Welch
2023-03-03  8:06   ` Krzysztof Kozlowski
2023-03-07 18:26     ` Martyn Welch
2023-03-08  8:41       ` Krzysztof Kozlowski
2023-03-08 20:58   ` Mathieu Poirier
2023-03-09 23:18     ` Hari Nagalla
2023-03-10 15:41       ` Mathieu Poirier
2023-03-24 10:31         ` Martyn Welch
2023-03-24 12:01     ` Martyn Welch [this message]
2023-03-02 17:14 ` [PATCH v3 2/3] remoteproc: k4: Split out functions common with M4 driver Martyn Welch
2023-03-08 21:45   ` Mathieu Poirier
2023-03-09 18:04   ` Hari Nagalla
2023-03-10  9:46     ` Martyn Welch
2023-03-10  9:53       ` AngeloGioacchino Del Regno
2023-03-10 13:55         ` Martyn Welch
2023-03-02 17:14 ` [PATCH v3 3/3] remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem Martyn Welch
2023-03-09 23:01   ` Mathieu Poirier

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=659687a489b4baea1f2cbb879fc59037b39f7ea0.camel@collabora.com \
    --to=martyn.welch@collabora.com \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --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.