linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
To: gregkh@linuxfoundation.org, robh+dt@kernel.org,
	stern@rowland.harvard.edu
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Hamish Martin <hamish.martin@alliedtelesis.co.nz>
Subject: [PATCH 2/2] dt-bindings: usb: generic-ohci: Document per-port-overcurrent property
Date: Fri,  4 Sep 2020 15:22:47 +1200	[thread overview]
Message-ID: <20200904032247.11345-3-hamish.martin@alliedtelesis.co.nz> (raw)
In-Reply-To: <20200904032247.11345-1-hamish.martin@alliedtelesis.co.nz>

OHCI overcurrent protection defaults to Global or "ganged" overcurrent
protection mode. This new property allows for the Individual Port
Over-current Protection to be selected when required.

Signed-off-by: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
---
 Documentation/devicetree/bindings/usb/generic-ohci.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml b/Documentation/devicetree/bindings/usb/generic-ohci.yaml
index 2178bcc401bc..5a68a647d059 100644
--- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml
+++ b/Documentation/devicetree/bindings/usb/generic-ohci.yaml
@@ -70,6 +70,11 @@ properties:
     description:
       Overrides the detected port count
 
+  per-port-overcurrent:
+    $ref: /schemas/types.yaml#/definitions/flag
+    description:
+      Set this flag for per-port overcurrent protection mode
+
   phys:
     description: PHY specifier for the USB PHY
 
-- 
2.28.0


      parent reply	other threads:[~2020-09-04  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  3:22 [PATCH 0/2] usb: ohci: Per-port overcurrent protection Hamish Martin
2020-09-04  3:22 ` [PATCH 1/2] usb: ohci: Add per-port overcurrent quirk Hamish Martin
2020-09-04 15:45   ` Alan Stern
2020-09-07  1:50     ` Hamish Martin
2020-09-07 14:59       ` stern
2020-09-07 22:28         ` Hamish Martin
2020-09-08 14:32           ` stern
2020-09-04  3:22 ` Hamish Martin [this message]

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=20200904032247.11345-3-hamish.martin@alliedtelesis.co.nz \
    --to=hamish.martin@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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).