From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Cc: Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org>,
Jassi Brar
<jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Santosh Shilimkar
<ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2 1/3] mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle
Date: Wed, 5 Aug 2015 23:29:23 -0700 [thread overview]
Message-ID: <20150806062923.GN16878@atomide.com> (raw)
In-Reply-To: <55C22C8E.3000506-l0cyMroinI0@public.gmane.org>
* Suman Anna <s-anna-l0cyMroinI0@public.gmane.org> [150805 08:35]:
> Hi Tony,
>
> On 08/05/2015 05:28 AM, Tony Lindgren wrote:
> > * Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org> [150717 13:59]:
> >> --- a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> +++ b/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> @@ -75,6 +75,14 @@ data that represent the following:
> >> Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
> >> associated with generating a tx/rx fifo interrupt.
> >>
> >> +Optional Properties:
> >> +--------------------
> >> +- ti,mbox-send-noirq: Quirk flag to allow the client user of this sub-mailbox
> >> + to send messages without triggering a Tx ready interrupt,
> >> + and to control the Tx ticker. Should be used only on
> >> + sub-mailboxes used to communicate with WkupM3 remote
> >> + processor on AM33xx/AM43xx SoCs.
> >> +
> >
> > Hmm can't you do this just by setting a flag in the device driver
> > based on the compatible string?
>
> We can't because there can be other users like PRUSS which will use a
> sub-mailbox in a regular fashion. The compatible serves the IP and there
> can be multiple sub-mailboxes underneath it, and this quirk is needed
> only on the one that's used by the WkupM3.
OK
> Do you have any comments on this?
Up to you guys then to figure out what property is used for it then.
Regards,
Tony
--
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: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] mailbox/omap: Add ti, mbox-send-noirq quirk to fix AM33xx CPU Idle
Date: Wed, 5 Aug 2015 23:29:23 -0700 [thread overview]
Message-ID: <20150806062923.GN16878@atomide.com> (raw)
In-Reply-To: <55C22C8E.3000506@ti.com>
* Suman Anna <s-anna@ti.com> [150805 08:35]:
> Hi Tony,
>
> On 08/05/2015 05:28 AM, Tony Lindgren wrote:
> > * Dave Gerlach <d-gerlach@ti.com> [150717 13:59]:
> >> --- a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> +++ b/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> @@ -75,6 +75,14 @@ data that represent the following:
> >> Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
> >> associated with generating a tx/rx fifo interrupt.
> >>
> >> +Optional Properties:
> >> +--------------------
> >> +- ti,mbox-send-noirq: Quirk flag to allow the client user of this sub-mailbox
> >> + to send messages without triggering a Tx ready interrupt,
> >> + and to control the Tx ticker. Should be used only on
> >> + sub-mailboxes used to communicate with WkupM3 remote
> >> + processor on AM33xx/AM43xx SoCs.
> >> +
> >
> > Hmm can't you do this just by setting a flag in the device driver
> > based on the compatible string?
>
> We can't because there can be other users like PRUSS which will use a
> sub-mailbox in a regular fashion. The compatible serves the IP and there
> can be multiple sub-mailboxes underneath it, and this quirk is needed
> only on the one that's used by the WkupM3.
OK
> Do you have any comments on this?
Up to you guys then to figure out what property is used for it then.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Dave Gerlach <d-gerlach@ti.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Santosh Shilimkar <ssantosh@kernel.org>,
Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH v2 1/3] mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle
Date: Wed, 5 Aug 2015 23:29:23 -0700 [thread overview]
Message-ID: <20150806062923.GN16878@atomide.com> (raw)
In-Reply-To: <55C22C8E.3000506@ti.com>
* Suman Anna <s-anna@ti.com> [150805 08:35]:
> Hi Tony,
>
> On 08/05/2015 05:28 AM, Tony Lindgren wrote:
> > * Dave Gerlach <d-gerlach@ti.com> [150717 13:59]:
> >> --- a/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> +++ b/Documentation/devicetree/bindings/mailbox/omap-mailbox.txt
> >> @@ -75,6 +75,14 @@ data that represent the following:
> >> Cell #3 (usr_id) - mailbox user id for identifying the interrupt line
> >> associated with generating a tx/rx fifo interrupt.
> >>
> >> +Optional Properties:
> >> +--------------------
> >> +- ti,mbox-send-noirq: Quirk flag to allow the client user of this sub-mailbox
> >> + to send messages without triggering a Tx ready interrupt,
> >> + and to control the Tx ticker. Should be used only on
> >> + sub-mailboxes used to communicate with WkupM3 remote
> >> + processor on AM33xx/AM43xx SoCs.
> >> +
> >
> > Hmm can't you do this just by setting a flag in the device driver
> > based on the compatible string?
>
> We can't because there can be other users like PRUSS which will use a
> sub-mailbox in a regular fashion. The compatible serves the IP and there
> can be multiple sub-mailboxes underneath it, and this quirk is needed
> only on the one that's used by the WkupM3.
OK
> Do you have any comments on this?
Up to you guys then to figure out what property is used for it then.
Regards,
Tony
next prev parent reply other threads:[~2015-08-06 6:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 20:56 [PATCH v2 0/3] soc: ti: Introduce wkup_m3_ipc driver Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` [PATCH v2 1/3] mailbox/omap: Add ti,mbox-send-noirq quirk to fix AM33xx CPU Idle Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` [PATCH v2 1/3] mailbox/omap: Add ti, mbox-send-noirq " Dave Gerlach
2015-08-05 10:28 ` [PATCH v2 1/3] mailbox/omap: Add ti,mbox-send-noirq " Tony Lindgren
2015-08-05 10:28 ` [PATCH v2 1/3] mailbox/omap: Add ti, mbox-send-noirq " Tony Lindgren
2015-08-05 15:32 ` [PATCH v2 1/3] mailbox/omap: Add ti,mbox-send-noirq " Suman Anna
2015-08-05 15:32 ` Suman Anna
2015-08-05 15:32 ` Suman Anna
[not found] ` <55C22C8E.3000506-l0cyMroinI0@public.gmane.org>
2015-08-06 6:29 ` Tony Lindgren [this message]
2015-08-06 6:29 ` Tony Lindgren
2015-08-06 6:29 ` [PATCH v2 1/3] mailbox/omap: Add ti, mbox-send-noirq " Tony Lindgren
2015-07-17 20:56 ` [PATCH v2 2/3] Documentation: dt: add bindings for TI Wakeup M3 IPC device Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` [PATCH v2 3/3] soc: ti: Add wkup_m3_ipc driver Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
2015-07-17 20:56 ` Dave Gerlach
[not found] ` <1437166592-25378-4-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2015-07-20 6:16 ` Tony Lindgren
2015-07-20 6:16 ` Tony Lindgren
2015-07-20 6:16 ` Tony Lindgren
2015-08-04 20:58 ` Dave Gerlach
2015-08-04 20:58 ` Dave Gerlach
2015-08-04 20:58 ` Dave Gerlach
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=20150806062923.GN16878@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=d-gerlach-l0cyMroinI0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=j-keerthy-l0cyMroinI0@public.gmane.org \
--cc=jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s-anna-l0cyMroinI0@public.gmane.org \
--cc=ssantosh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.