linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: aisheng.dong@nxp.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/5] dt-bindings: mailbox: allow mbox-cells to be equal to 0
Date: Sun,  8 Jul 2018 22:56:53 +0800	[thread overview]
Message-ID: <1531061817-1980-2-git-send-email-aisheng.dong@nxp.com> (raw)
In-Reply-To: <1531061817-1980-1-git-send-email-aisheng.dong@nxp.com>

Mailbox devices may have only one channel which means the mbox-cells
at least 1 does not make sense for this type devices. Let's remove
that limitation to allow the mbox-cells to be equal to 0.

Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: devicetree at vger.kernel.org
Cc: linux-kernel at vger.kernel.org
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
---
ChangeLog:
 * New patch introduced in v3 series
 * Actually there're already users in kernel with mbox-cells set to 0.
   See:
   arch/arm/boot/dts/bcm283x.dtsi:145: #mbox-cells = <0>;
---
 Documentation/devicetree/bindings/mailbox/mailbox.txt | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/mailbox/mailbox.txt b/Documentation/devicetree/bindings/mailbox/mailbox.txt
index af8ecee..c2fcd05 100644
--- a/Documentation/devicetree/bindings/mailbox/mailbox.txt
+++ b/Documentation/devicetree/bindings/mailbox/mailbox.txt
@@ -6,8 +6,7 @@ assign appropriate mailbox channel to client drivers.
 * Mailbox Controller
 
 Required property:
-- #mbox-cells: Must be at least 1. Number of cells in a mailbox
-		specifier.
+- #mbox-cells: Number of cells in a mailbox specifier.
 
 Example:
 	mailbox: mailbox {
-- 
2.7.4

  reply	other threads:[~2018-07-08 14:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08 14:56 [PATCH V4 0/5] soc: imx: add scu firmware api support Dong Aisheng
2018-07-08 14:56 ` Dong Aisheng [this message]
2018-07-08 14:56 ` [PATCH V4 2/5] dt-bindings: arm: fsl: add mu binding doc Dong Aisheng
2018-07-11 15:09   ` Rob Herring
2018-07-08 14:56 ` [PATCH V4 3/5] mailbox: imx: add imx mu support Dong Aisheng
2018-07-10 14:19   ` Sascha Hauer
2018-07-11  7:29     ` A.s. Dong
2018-07-11  7:54       ` Sascha Hauer
2018-07-11 10:37         ` A.s. Dong
2018-07-11 10:44           ` Jassi Brar
2018-07-11 12:58             ` A.s. Dong
2018-07-11 16:31               ` Jassi Brar
2018-07-11 16:41                 ` A.s. Dong
2018-07-11 17:00                   ` Jassi Brar
2018-07-12  4:06                     ` A.s. Dong
2018-07-11 13:30       ` Peng Fan
2018-07-08 14:56 ` [PATCH V4 4/5] dt-bindings: arm: fsl: add scu binding doc Dong Aisheng
2018-07-11 15:08   ` Rob Herring
2018-07-12 11:04     ` A.s. Dong
2018-07-08 14:56 ` [PATCH V4 5/5] soc: imx: add SC firmware IPC and APIs Dong Aisheng
2018-07-10 14:44   ` Sascha Hauer
2018-07-11  9:18     ` A.s. Dong
2018-07-11 10:31       ` Sascha Hauer
2018-07-11 11:27         ` A.s. Dong
2018-07-11 16:49 ` [PATCH V4 0/5] soc: imx: add scu firmware api support Sudeep Holla
2018-07-12  3:46   ` A.s. Dong
2018-07-12 10:32     ` Sudeep Holla
2018-07-12 12:29       ` Leonard Crestez

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=1531061817-1980-2-git-send-email-aisheng.dong@nxp.com \
    --to=aisheng.dong@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).