Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp3177158rwb; Fri, 9 Dec 2022 10:55:47 -0800 (PST) X-Google-Smtp-Source: AA0mqf5jl5mv2PEEboe3DmFoHXGCnZNZuTcVQ64DOeQv+dls6pV5RLutxO/n93/TD6tAn8b+PqkD X-Received: by 2002:a17:906:4e9a:b0:7c0:b292:e56b with SMTP id v26-20020a1709064e9a00b007c0b292e56bmr5358949eju.68.1670612147204; Fri, 09 Dec 2022 10:55:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670612147; cv=none; d=google.com; s=arc-20160816; b=dXQi8AugkWEEwhOamy9j17VuSUlfiU+kTQBPBYg0lzIQuoumOFa6GGwXgpJx4BiYIC X/X+U3Hte3B3FDFXFJFZ8j64Z5TcZBm6l6GHlc6wN2tCMCIw2BgxfBXxcMMc1tTGJpFC ZnOwuz0nCyAtK8Titx1nH6aGDNtO6j1tdzqcm3ukKRAJ8RF8CdpMvBxhn/WVJZcTtkf5 6PCNb3qpk1yqXNSQUCmvI5vVfkand069U//0DRemsM8l5XJuE4ksDQ6pLcMJ1x+y7X/2 u8MJmCa6p69q1SQ828DlJvw0fcJGnHDYyPDhmWCOlYrHeuRNkz07pgmEoEtUld732y6a f3wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=d68uD8NtMOQAm9gTfodbUYj478P68XPNWB5DAuDrMdk=; b=k+j+4w160MMS9+Kl5tHCfWW/NDptVuE9nWya3ye7NVK0/LIp0xpyaWw5i2UMku0o9j IbXNDJcgu4z0RADof/C5PPiNBuhm9XfVnIdx/kjMSjFO+zPV7Wt81qp3uTN31CGq1Lwa PeqBH7d4n9Lef/chcqZV1hrF46rocO/jC5HtDO44tN2rFKIzm7jtA9Ja3TX3wMBS2gtq XRMh1INwQfPXfL5uep7XZlb1lk0utj3HlT1j750HIaJRMX/n6U3dYMSWegZCzNcqlZoh D1y9THN1FFZGnI1qDmkiWvnXejUGGxVCoZOSl4P1QbAvgCyTfSpo2oIRPunD+AvN6ouL o7Mw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=F1S6Ycl3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qa39-20020a17090786a700b007c07a807a78si425060ejc.215.2022.12.09.10.55.28; Fri, 09 Dec 2022 10:55:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=F1S6Ycl3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229976AbiLISnA (ORCPT + 74 others); Fri, 9 Dec 2022 13:43:00 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32770 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229951AbiLISmx (ORCPT ); Fri, 9 Dec 2022 13:42:53 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EE795C76B; Fri, 9 Dec 2022 10:42:51 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8A3B2622FE; Fri, 9 Dec 2022 18:42:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F09FDC433EF; Fri, 9 Dec 2022 18:42:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670611371; bh=PpE/G/4dvnSSAm8Q7Pn2IAc5LMvy9D6cw/GCLldO0ms=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=F1S6Ycl3LrDQuNE7lflcCF9ALoe/dSaR0vWZv/KPyaGuzx5CDdcOsTvPmrszRAt6h MbgC3lOeF+nfVAE5h2KKDRMqyR8zOPu4l08ZXCEdV8L361DTKlZ6jZEd5pnhz1HviI FVafqAjov2Z2kNFV1zN85bPLqyK5PyWgvox3UdZSJb/p9Nz/l0Kuz64QK+d2yz99fK WDMJX8IRE6t2WwjAfOx67ONytkso+oFnWzzPaV1bnqtaHqI7SOeil28bR8jVa2os0o TMzBBZ4PruxP4u5F8sNn2LUPGaD1GbGOjUmaLWin4ZBsg93tv+EqjziZhmSq4JMd5p qPUeYjzTmKz1A== Received: by mail-ua1-f50.google.com with SMTP id m5so1557829uah.3; Fri, 09 Dec 2022 10:42:50 -0800 (PST) X-Gm-Message-State: ANoB5pmZGUEtTazTkIGIMi9ruI7pE1TR526lmUZZgTAZDcDZ18CBpqh5 p1PEm3jXepkTWwQC7AOjthSCovahG9jPFnQbQQ== X-Received: by 2002:ab0:3a96:0:b0:419:678:cf31 with SMTP id r22-20020ab03a96000000b004190678cf31mr34441960uaw.63.1670611369881; Fri, 09 Dec 2022 10:42:49 -0800 (PST) MIME-Version: 1.0 References: <20221209171621.3351220-1-robh@kernel.org> In-Reply-To: <20221209171621.3351220-1-robh@kernel.org> From: Rob Herring Date: Fri, 9 Dec 2022 12:42:38 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] dt-bindings: mmc: Convert Fujitsu SDHCI to DT schema To: Ulf Hansson , Krzysztof Kozlowski Cc: Ard Biesheuvel , Ilias Apalodimas , linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 9, 2022 at 11:16 AM Rob Herring wrote: > > Convert the Fujitsu SDHCI binding to DT schema format. > > The interrupts were not documented. The driver only uses the first > interrupt, but the DT and example have 2 interrupts. The 2nd one is > unknown. "dma-coherent" was also not documented, but is used. > > The "socionext,synquacer-sdhci" compatible was not documented, but it is > compatible with "fujitsu,mb86s70-sdhci-3.0.yaml" and is in use (in > u-boot Synquacer dts). > > Signed-off-by: Rob Herring > --- > .../mmc/fujitsu,mb86s70-sdhci-3.0.yaml | 67 +++++++++++++++++++ > .../devicetree/bindings/mmc/sdhci-fujitsu.txt | 32 --------- > 2 files changed, 67 insertions(+), 32 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mmc/fujitsu,mb86s70-sdhci-3.0.yaml > delete mode 100644 Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt > > diff --git a/Documentation/devicetree/bindings/mmc/fujitsu,mb86s70-sdhci-3.0.yaml b/Documentation/devicetree/bindings/mmc/fujitsu,mb86s70-sdhci-3.0.yaml > new file mode 100644 > index 000000000000..0218a6ce4b2f > --- /dev/null > +++ b/Documentation/devicetree/bindings/mmc/fujitsu,mb86s70-sdhci-3.0.yaml > @@ -0,0 +1,67 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mmc/fujitsu,mb86s70-sdhci-3.0.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Fujitsu SDHCI controller > + > +maintainers: > + - Vincent Yang Bounces. Any other volunteers? > + > +allOf: > + - $ref: mmc-controller.yaml# > + > +properties: > + compatible: > + oneOf: > + - items: > + - const: socionext,synquacer-sdhci > + - const: fujitsu,mb86s70-sdhci-3.0 > + - const: fujitsu,mb86s70-sdhci-3.0 > + > + reg: > + maxItems: 1 > + > + clocks: > + items: > + - description: Core clock > + - description: Interface clock > + > + clock-names: > + items: > + - const: core > + - const: iface > + > + dma-coherent: true > + > + interrupts: > + maxItems: 2 > + > + fujitsu,cmd-dat-delay-select: > + type: boolean > + description: Indicating that the host requires the CMD_DAT_DELAY control > + to be enabled. > + > +required: > + - compatible > + - reg > + - clocks > + - clock-names > + - interrupts > + > +unevaluatedProperties: false > + > +examples: > + - | > + mmc@36600000 { > + compatible = "fujitsu,mb86s70-sdhci-3.0"; > + reg = <0x36600000 0x1000>; > + interrupts = <0 172 0x4>, > + <0 173 0x4>; > + bus-width = <4>; > + vqmmc-supply = <&vccq_sdhci1>; > + clocks = <&clock 2 2 0>, <&clock 2 3 0>; > + clock-names = "core", "iface"; > + }; > +... > diff --git a/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt b/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt > deleted file mode 100644 > index 3ee9263adf73..000000000000 > --- a/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt > +++ /dev/null > @@ -1,32 +0,0 @@ > -* Fujitsu SDHCI controller > - > -This file documents differences between the core properties in mmc.txt > -and the properties used by the sdhci_f_sdh30 driver. > - > -Required properties: > -- compatible: "fujitsu,mb86s70-sdhci-3.0" > -- clocks: Must contain an entry for each entry in clock-names. It is a > - list of phandles and clock-specifier pairs. > - See ../clocks/clock-bindings.txt for details. > -- clock-names: Should contain the following two entries: > - "iface" - clock used for sdhci interface > - "core" - core clock for sdhci controller > - > -Optional properties: > -- vqmmc-supply: phandle to the regulator device tree node, mentioned > - as the VCCQ/VDD_IO supply in the eMMC/SD specs. > -- fujitsu,cmd-dat-delay-select: boolean property indicating that this host > - requires the CMD_DAT_DELAY control to be enabled. > - > -Example: > - > - sdhci1: mmc@36600000 { > - compatible = "fujitsu,mb86s70-sdhci-3.0"; > - reg = <0 0x36600000 0x1000>; > - interrupts = <0 172 0x4>, > - <0 173 0x4>; > - bus-width = <4>; > - vqmmc-supply = <&vccq_sdhci1>; > - clocks = <&clock 2 2 0>, <&clock 2 3 0>; > - clock-names = "iface", "core"; > - }; > -- > 2.35.1 >