From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Hansson Subject: Re: [PATCH v3 1/2] dt-bindings: mmc: Add YAML schemas for the generic MMC options Date: Tue, 28 May 2019 10:40:16 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Maxime Ripard Cc: Mark Rutland , DTML , Rob Herring , "linux-mmc@vger.kernel.org" , Chen-Yu Tsai , Rob Herring , Frank Rowand , Linux ARM List-Id: devicetree@vger.kernel.org > +patternProperties: > + "^.*@[0-9]+$": > + properties: > + reg: > + items: > + - minimum: 0 > + maximum: 7 > + description: > + Must contain the SDIO function number of the function this > + subnode describes. A value of 0 denotes the memory SD > + function, values from 1 to 7 denote the SDIO functions. > + > + broken-hpi: > + $ref: /schemas/types.yaml#/definitions/flag > + description: > + Use this to indicate that the mmc-card has a broken hpi > + implementation, and that hpi should not be used. > + > + required: > + - reg > + [...] > -Use of Function subnodes > ------------------------- > - > -On embedded systems the cards connected to a host may need additional > -properties. These can be specified in subnodes to the host controller node. > -The subnodes are identified by the standard 'reg' property. > -Which information exactly can be specified depends on the bindings for the > -SDIO function driver for the subnode, as specified by the compatible string. > - > -Required host node properties when using function subnodes: > -- #address-cells: should be one. The cell is the slot id. > -- #size-cells: should be zero. > - > -Required function subnode properties: > -- reg: Must contain the SDIO function number of the function this subnode > - describes. A value of 0 denotes the memory SD function, values from > - 1 to 7 denote the SDIO functions. > - > -Optional function subnode properties: > -- compatible: name of SDIO function following generic names recommended practice > - I think most of the information of how we use sub(child) nodes disappeared in this conversion - or at least gets harder to understand. Could we perhaps keep some of this? Kind regards Uffe From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5FE03C04AB6 for ; Tue, 28 May 2019 08:41:01 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 220CE2075B for ; Tue, 28 May 2019 08:41:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="quVBHBQJ"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="GgRPe8E2" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 220CE2075B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Z4z7cZKNFNxYpZ0QSbQiSSctwxqdcKzsKAlgphtDymQ=; b=quVBHBQJvPqYTR 8xkPyyc+2rScWplCmWgPeOuRf+WgkETatuVNGPpFCKtY7qU22qganKqSzsqSYBBxBtMvSaJ2U4DoA 5ZcBEX7DqVexT6wESmcCfa35vqGURho5WHHgk2WYphlB6KfV+PgV2K2cz2C729Xnu5L8aOVFeqHra QbUUn7nZF/t3tQrr1CUbIDTFfh4MVsNss/b4RBoWVRwR3AZvho6Hjh0a1mf3yn9KEXIntFseNEPRL 8GC4lUWdCjD76xGOuLlfOBLcVkPWLHxDO5FcIYDLRSX1+ZKVfTN+71uqBGaoT0KmuQOco9s0z6XDK ftE280CjHIPVlfVdJJsg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVXfF-0003oe-8e; Tue, 28 May 2019 08:40:57 +0000 Received: from mail-vk1-xa43.google.com ([2607:f8b0:4864:20::a43]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVXfB-0003nX-Oz for linux-arm-kernel@lists.infradead.org; Tue, 28 May 2019 08:40:55 +0000 Received: by mail-vk1-xa43.google.com with SMTP id p24so4460916vki.5 for ; Tue, 28 May 2019 01:40:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L1gEe0Qo8uUw419whddZefVmtI1Y7WOAQp/Jh1nRbBY=; b=GgRPe8E23Cer8Df2SQau1m/3AEgbXMJIUf9Mzz4H1Om4WYidE64+qFE0cnf2/qjdNf nKzLE1aUuA7hdhVAZe14ZNmicWNfhS1TTTf5mBvhC7KDo66j5v/uS1D8RXfibCDbLeV7 tXRUgxh9BcrEvkxi36Qg9Wbw9z+Yw8Px/cW0AQ5a1Dk3rPxG64mXomNtsK7uTlKcWNYt gaBEsdD968TJcWOLIRFic9Kp+v7xkMoS/oHh/8MkM79TkCssqljli4Hl71gkjer7ydLp dLGjYQlGrdurQYJsGv4mLcyblN9hl5NEF0wVIgI9ES+8Gm84uPI6v72NFa4dNnEqocjE t9/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L1gEe0Qo8uUw419whddZefVmtI1Y7WOAQp/Jh1nRbBY=; b=dqdQeAZTFesLfZOXMa7rxt30TnnR+rQjOdWMqvr9b+J8Cz00/Wxtu6yLh7CAAlQHww iPTdeBtKWyL4dMk4+uTZHcf1JcyYb5r1D2KQdFZej5Eqsc6DabCeX57R0rO0z77vSxsf DrrdQ3AjeW1Q2Xn7wrTwLueDKEC9dXrzTx1wz/mc5fVE5onxy5nifmz2gH5IR5WK7oSd G1ZuZudWeqDGD6m01IJ0YFusTvnqMtWPEglC9YfcVtEUn2TukYvPr/zGtyvFtp4U49Ad KSASq3ixNfROw5pXjdVR3CCVIOoKhb6XyJ86fRTO2snT08urorBslY6nK95FAATcMVuU qL+Q== X-Gm-Message-State: APjAAAVFveIl1I4SDi2PY8/ZZdYE7Ib0+j60ebzPbHzXtfBvD/fn1+aV /eT/9Prg2OAHv0W3xsXJmZl9d52djhqzbgeWaLU3oA== X-Google-Smtp-Source: APXvYqx7LhK72f0luzwT93lolmN9FxjSTp2ZQy1E52COyZc/gaMuKcVA6k4ogJNFhunQ6qfXUyFIxCroR3vUPGJZ9Zw= X-Received: by 2002:a1f:bc4b:: with SMTP id m72mr2400696vkf.36.1559032852442; Tue, 28 May 2019 01:40:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ulf Hansson Date: Tue, 28 May 2019 10:40:16 +0200 Message-ID: Subject: Re: [PATCH v3 1/2] dt-bindings: mmc: Add YAML schemas for the generic MMC options To: Maxime Ripard X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190528_014053_814345_428150D6 X-CRM114-Status: GOOD ( 15.17 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , DTML , Rob Herring , "linux-mmc@vger.kernel.org" , Chen-Yu Tsai , Rob Herring , Frank Rowand , Linux ARM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org > +patternProperties: > + "^.*@[0-9]+$": > + properties: > + reg: > + items: > + - minimum: 0 > + maximum: 7 > + description: > + Must contain the SDIO function number of the function this > + subnode describes. A value of 0 denotes the memory SD > + function, values from 1 to 7 denote the SDIO functions. > + > + broken-hpi: > + $ref: /schemas/types.yaml#/definitions/flag > + description: > + Use this to indicate that the mmc-card has a broken hpi > + implementation, and that hpi should not be used. > + > + required: > + - reg > + [...] > -Use of Function subnodes > ------------------------- > - > -On embedded systems the cards connected to a host may need additional > -properties. These can be specified in subnodes to the host controller node. > -The subnodes are identified by the standard 'reg' property. > -Which information exactly can be specified depends on the bindings for the > -SDIO function driver for the subnode, as specified by the compatible string. > - > -Required host node properties when using function subnodes: > -- #address-cells: should be one. The cell is the slot id. > -- #size-cells: should be zero. > - > -Required function subnode properties: > -- reg: Must contain the SDIO function number of the function this subnode > - describes. A value of 0 denotes the memory SD function, values from > - 1 to 7 denote the SDIO functions. > - > -Optional function subnode properties: > -- compatible: name of SDIO function following generic names recommended practice > - I think most of the information of how we use sub(child) nodes disappeared in this conversion - or at least gets harder to understand. Could we perhaps keep some of this? Kind regards Uffe _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel