All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Bostic <cbostic@linux.vnet.ibm.com>
To: joel@jms.id.au, jk@ozlabs.org
Cc: Christopher Bostic <cbostic@linux.vnet.ibm.com>,
	openbmc@lists.ozlabs.org
Subject: [PATCH linux dev-4.10 v2 2/3] ARM: dts: fsi: Add optional master property no-scan-on-init
Date: Thu,  3 Aug 2017 22:26:21 -0500	[thread overview]
Message-ID: <20170804032622.88674-3-cbostic@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170804032622.88674-1-cbostic@linux.vnet.ibm.com>

Add new optional master property no-scan-on-init that specifies
that at master init time it should not scan for connected devices.
This is necessary in cases where a scan could interfere with
other connected FSI masters on the same bus.

Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>
---
 arch/arm/boot/dts/ibm-power9-cfam.dtsi | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/boot/dts/ibm-power9-cfam.dtsi b/arch/arm/boot/dts/ibm-power9-cfam.dtsi
index 5630e02..55fb58f 100644
--- a/arch/arm/boot/dts/ibm-power9-cfam.dtsi
+++ b/arch/arm/boot/dts/ibm-power9-cfam.dtsi
@@ -128,6 +128,8 @@
 			#address-cells = <2>;
 			#size-cells = <0>;
 
+			no-scan-on-init;
+
 			cfam@1,0 {
 				reg = <1 0>;
 				#address-cells = <1>;
-- 
1.8.2.2

  parent reply	other threads:[~2017-08-04  3:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  3:26 [PATCH linux dev-4.10 v2 0/3] Add FSI master scan conditional Christopher Bostic
2017-08-04  3:26 ` [PATCH linux dev-4.10 v2 1/3] dt-bindings: fsi: Add optional property no-scan-on-init Christopher Bostic
2017-08-04  3:26 ` Christopher Bostic [this message]
2017-08-04  3:26 ` [PATCH linux dev-4.10 v2 3/3] fsi: core: Add check for master " Christopher Bostic
2017-08-04  3:33   ` Jeremy Kerr
2017-08-08 13:02     ` Joel Stanley

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=20170804032622.88674-3-cbostic@linux.vnet.ibm.com \
    --to=cbostic@linux.vnet.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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.