From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Documentation: dt: mailbox: Add TI Message Manager
Date: Tue, 9 Feb 2016 06:31:44 -0600 [thread overview]
Message-ID: <56B9DC30.5040806@ti.com> (raw)
In-Reply-To: <CABb+yY3kGq_R49Xx4fK3UMqtuFiuv-pXJWvjkEFLPL9xRu5T4A@mail.gmail.com>
On 02/08/2016 10:14 PM, Jassi Brar wrote:
Thanks for the review.
> On Fri, Feb 5, 2016 at 10:04 PM, Nishanth Menon <nm@ti.com> wrote:
>> +
>> + msgmgr: msgmgr at 02a00000 {
>> + compatible = "ti,k2g-message-manager", "ti,message-manager";
>> + #mbox-cells = <1>;
>> + reg-names = "queue_proxy_region", "queue_state_debug_region";
>> + reg = <0x02a00000 0x400000>, <0x028c3400 0x400>;
>> +
>> + msgmgr_proxy_pmmc_tx_prio0: pmmc_tx_prio0 {
>> + ti,queue-id = <0>;
>> + ti,proxy-id = <0>;
>> + };
>> +
>> + msgmgr_proxy_pmmc_rx: pmmc_rx {
>> + ti,queue-id = <5>;
>> + ti,proxy-id = <2>;
>> + interrupt-names = "rx";
>> + interrupts = <GIC_SPI 324 IRQ_TYPE_EDGE_RISING>;
>> + };
>> + };
>> +
> I think we should get rid of consumer specifics from the provider node...
If I get rid of the consumer nodes, how do you propose I describe the rx
queue interrupt(s) in the msmgr dt node (Every Rx queue will have it's
own interrupt - and it cannot be reverse computed from queue ID, proxy ID)?
>> +...
>> + pmmc {
>> + ...
>> + mbox-names = "tx", "rx";
>> + mboxes = <&msgmgr &msgmgr_proxy_pmmc_tx>
>> + <&msgmgr &msgmgr_proxy_pmmc_rx>;
>> + ...
>> + };
>>
> ... and have consumers like
> pmmc {
> ...
> mbox-names = "tx", "rx";
> mboxes = <&msgmgr 0 0>
> <&msgmgr 5 2>;
> };
>
> I leave the IRQ for you to decide how to specify - a 'dummy' or
> 'valid' always provided as last cell in mboxes or some other way.
> (I'll review other patches in detail later)
What do we do with the issues that Suman pointed out in the mailbox
framework itself? Could you respond to that thread[1] as well?
[1] http://marc.info/?l=devicetree&m=145496308418123&w=2
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
To: Jassi Brar
<jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Cc: Devicetree List
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Franklin S Cooper Jr <fcooper-l0cyMroinI0@public.gmane.org>,
Santosh Shilimkar
<ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 1/2] Documentation: dt: mailbox: Add TI Message Manager
Date: Tue, 9 Feb 2016 06:31:44 -0600 [thread overview]
Message-ID: <56B9DC30.5040806@ti.com> (raw)
In-Reply-To: <CABb+yY3kGq_R49Xx4fK3UMqtuFiuv-pXJWvjkEFLPL9xRu5T4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/08/2016 10:14 PM, Jassi Brar wrote:
Thanks for the review.
> On Fri, Feb 5, 2016 at 10:04 PM, Nishanth Menon <nm-l0cyMroinI0@public.gmane.org> wrote:
>> +
>> + msgmgr: msgmgr@02a00000 {
>> + compatible = "ti,k2g-message-manager", "ti,message-manager";
>> + #mbox-cells = <1>;
>> + reg-names = "queue_proxy_region", "queue_state_debug_region";
>> + reg = <0x02a00000 0x400000>, <0x028c3400 0x400>;
>> +
>> + msgmgr_proxy_pmmc_tx_prio0: pmmc_tx_prio0 {
>> + ti,queue-id = <0>;
>> + ti,proxy-id = <0>;
>> + };
>> +
>> + msgmgr_proxy_pmmc_rx: pmmc_rx {
>> + ti,queue-id = <5>;
>> + ti,proxy-id = <2>;
>> + interrupt-names = "rx";
>> + interrupts = <GIC_SPI 324 IRQ_TYPE_EDGE_RISING>;
>> + };
>> + };
>> +
> I think we should get rid of consumer specifics from the provider node...
If I get rid of the consumer nodes, how do you propose I describe the rx
queue interrupt(s) in the msmgr dt node (Every Rx queue will have it's
own interrupt - and it cannot be reverse computed from queue ID, proxy ID)?
>> +...
>> + pmmc {
>> + ...
>> + mbox-names = "tx", "rx";
>> + mboxes = <&msgmgr &msgmgr_proxy_pmmc_tx>
>> + <&msgmgr &msgmgr_proxy_pmmc_rx>;
>> + ...
>> + };
>>
> ... and have consumers like
> pmmc {
> ...
> mbox-names = "tx", "rx";
> mboxes = <&msgmgr 0 0>
> <&msgmgr 5 2>;
> };
>
> I leave the IRQ for you to decide how to specify - a 'dummy' or
> 'valid' always provided as last cell in mboxes or some other way.
> (I'll review other patches in detail later)
What do we do with the issues that Suman pointed out in the mailbox
framework itself? Could you respond to that thread[1] as well?
[1] http://marc.info/?l=devicetree&m=145496308418123&w=2
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>, Nishanth Menon <nm@ti.com>
Cc: Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Franklin S Cooper Jr <fcooper@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] Documentation: dt: mailbox: Add TI Message Manager
Date: Tue, 9 Feb 2016 06:31:44 -0600 [thread overview]
Message-ID: <56B9DC30.5040806@ti.com> (raw)
In-Reply-To: <CABb+yY3kGq_R49Xx4fK3UMqtuFiuv-pXJWvjkEFLPL9xRu5T4A@mail.gmail.com>
On 02/08/2016 10:14 PM, Jassi Brar wrote:
Thanks for the review.
> On Fri, Feb 5, 2016 at 10:04 PM, Nishanth Menon <nm@ti.com> wrote:
>> +
>> + msgmgr: msgmgr@02a00000 {
>> + compatible = "ti,k2g-message-manager", "ti,message-manager";
>> + #mbox-cells = <1>;
>> + reg-names = "queue_proxy_region", "queue_state_debug_region";
>> + reg = <0x02a00000 0x400000>, <0x028c3400 0x400>;
>> +
>> + msgmgr_proxy_pmmc_tx_prio0: pmmc_tx_prio0 {
>> + ti,queue-id = <0>;
>> + ti,proxy-id = <0>;
>> + };
>> +
>> + msgmgr_proxy_pmmc_rx: pmmc_rx {
>> + ti,queue-id = <5>;
>> + ti,proxy-id = <2>;
>> + interrupt-names = "rx";
>> + interrupts = <GIC_SPI 324 IRQ_TYPE_EDGE_RISING>;
>> + };
>> + };
>> +
> I think we should get rid of consumer specifics from the provider node...
If I get rid of the consumer nodes, how do you propose I describe the rx
queue interrupt(s) in the msmgr dt node (Every Rx queue will have it's
own interrupt - and it cannot be reverse computed from queue ID, proxy ID)?
>> +...
>> + pmmc {
>> + ...
>> + mbox-names = "tx", "rx";
>> + mboxes = <&msgmgr &msgmgr_proxy_pmmc_tx>
>> + <&msgmgr &msgmgr_proxy_pmmc_rx>;
>> + ...
>> + };
>>
> ... and have consumers like
> pmmc {
> ...
> mbox-names = "tx", "rx";
> mboxes = <&msgmgr 0 0>
> <&msgmgr 5 2>;
> };
>
> I leave the IRQ for you to decide how to specify - a 'dummy' or
> 'valid' always provided as last cell in mboxes or some other way.
> (I'll review other patches in detail later)
What do we do with the issues that Suman pointed out in the mailbox
framework itself? Could you respond to that thread[1] as well?
[1] http://marc.info/?l=devicetree&m=145496308418123&w=2
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2016-02-09 12:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:34 [PATCH 0/2] mailbox: Introduce Texas Instrument's message manager driver Nishanth Menon
2016-02-05 16:34 ` Nishanth Menon
2016-02-05 16:34 ` Nishanth Menon
2016-02-05 16:34 ` [PATCH 1/2] Documentation: dt: mailbox: Add TI Message Manager Nishanth Menon
2016-02-05 16:34 ` Nishanth Menon
2016-02-05 16:34 ` Nishanth Menon
2016-02-08 19:37 ` Rob Herring
2016-02-08 19:37 ` Rob Herring
2016-02-08 19:37 ` Rob Herring
2016-02-08 20:23 ` Suman Anna
2016-02-08 20:23 ` Suman Anna
2016-02-08 20:23 ` Suman Anna
2016-02-08 21:18 ` Rob Herring
2016-02-08 20:31 ` Nishanth Menon
2016-02-08 20:31 ` Nishanth Menon
2016-02-08 20:31 ` Nishanth Menon
2016-02-09 4:14 ` Jassi Brar
2016-02-09 4:14 ` Jassi Brar
2016-02-09 12:31 ` Nishanth Menon [this message]
2016-02-09 12:31 ` Nishanth Menon
2016-02-09 12:31 ` Nishanth Menon
2016-02-09 14:54 ` Jassi Brar
2016-02-09 14:54 ` Jassi Brar
2016-02-09 15:35 ` Jassi Brar
2016-02-09 15:35 ` Jassi Brar
2016-02-09 15:35 ` Jassi Brar
2016-02-09 15:43 ` Nishanth Menon
2016-02-09 15:43 ` Nishanth Menon
2016-02-09 15:43 ` Nishanth Menon
2016-02-09 18:10 ` Nishanth Menon
2016-02-09 18:10 ` Nishanth Menon
2016-02-09 18:10 ` Nishanth Menon
2016-02-10 20:13 ` Suman Anna
2016-02-10 20:13 ` Suman Anna
2016-02-10 20:51 ` Nishanth Menon
2016-02-10 20:51 ` Nishanth Menon
2016-02-10 20:51 ` Nishanth Menon
2016-02-11 4:23 ` Jassi Brar
2016-02-11 4:23 ` Jassi Brar
2016-02-11 4:23 ` Jassi Brar
2016-02-11 5:03 ` Nishanth Menon
2016-02-11 5:03 ` Nishanth Menon
2016-02-11 5:03 ` Nishanth Menon
2016-02-26 11:59 ` Jassi Brar
2016-02-26 11:59 ` Jassi Brar
2016-02-26 11:59 ` Jassi Brar
2016-02-26 22:30 ` Nishanth Menon
2016-02-26 22:30 ` Nishanth Menon
2016-02-05 16:34 ` [PATCH 2/2] mailbox: Introduce TI message manager driver Nishanth Menon
2016-02-05 16:34 ` Nishanth Menon
2016-02-05 16:34 ` 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=56B9DC30.5040806@ti.com \
--to=nm@ti.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.