From patchwork Thu Feb 28 14:33:44 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?b?TcOlbnMgUnVsbGfDpXJk?= X-Patchwork-Id: 1049530 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=mansr.com Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 449FRc5jNrz9s2R for ; Fri, 1 Mar 2019 01:34:04 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730965AbfB1Od6 (ORCPT ); Thu, 28 Feb 2019 09:33:58 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:47880 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725918AbfB1Od6 (ORCPT ); Thu, 28 Feb 2019 09:33:58 -0500 Received: by unicorn.mansr.com (Postfix, from userid 51770) id 3232015632; Thu, 28 Feb 2019 14:33:56 +0000 (GMT) From: Mans Rullgard To: Rob Herring , Mark Rutland Cc: Greg Kroah-Hartman , linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC][PATCH] dt-bindings: usb: add non-removable device property Date: Thu, 28 Feb 2019 14:33:44 +0000 Message-Id: <20190228143344.16312-1-mans@mansr.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Add a boolean property indicating that a device is hardwired to the upstream port. Although hubs can provide this information, they are not always configured correctly. An alternate means of indicating this for built-in USB devices is thus useful. Signed-off-by: Mans Rullgard --- I have a situation where userspace would like to know which USB devices are built-in, but the on-board hub doesn't have the right setting. Also, the hub itself can't be indicated as fixed in any other way that I'm aware of. In a way, adding this property seems a bit silly since dt can only sensibly be used for hardwired devices in the first place. Thus the mere presence of a dt node could be taken to indicate the same thing. On the other hand, it's conceivable that someone might dynamically generate a devicetree based on what happens to be connected on boot or something. For that reason, and explicit property seems safer. --- Documentation/devicetree/bindings/usb/usb-device.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt b/Documentation/devicetree/bindings/usb/usb-device.txt index 036be172b1ae..903d39b7e415 100644 --- a/Documentation/devicetree/bindings/usb/usb-device.txt +++ b/Documentation/devicetree/bindings/usb/usb-device.txt @@ -26,6 +26,10 @@ Required properties for device nodes: - reg: the number of the USB hub port or the USB host-controller port to which this device is attached. The range is 1-255. +Optional properties for device nodes: +- non-removable: boolean, if present the device is hardwired to the + upstream port. + Required properties for device nodes with interface nodes: - #address-cells: shall be 2 @@ -55,6 +59,10 @@ Required properties for combined nodes: - reg: the number of the USB hub port or the USB host-controller port to which this device is attached. The range is 1-255. +Optional properties for combined nodes: +- non-removable: boolean, if present the device is hardwired to the + upstream port. + Required properties for hub nodes with device nodes: - #address-cells: shall be 1