Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4307114pxj; Tue, 8 Jun 2021 11:05:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxxh35sYLHS9lPU1y34R6ppbTemfLSQrj5WzbTLCPTEqt12CcfiZo/HK7bIJrAMZXhur3Er X-Received: by 2002:a50:eb47:: with SMTP id z7mr27273539edp.68.1623175537385; Tue, 08 Jun 2021 11:05:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623175537; cv=none; d=google.com; s=arc-20160816; b=Hf9SZhw5/LaCYK9+odnV6ZVDxEpqpmQgbD7+N+2qHeSev2miGaDxEGfOmOU5O/Jl2B HjJIubEBXRMs0UuHjIIJqZKA/kiDftRijx9oDbjcCwiQ+YwrMCyelYtl8bikmnx0U4ej 7zr651eW6EVEilrMEMgJWfglWUloJV73KMXHndU5fmfTI/bjtDyFnVSIRy+RNNEUuM8W tqkfzUtAmMKmX6WNuzpI2MmTLRwJLKYrOxb9h5LHacWJC+Axx/EKTWgnP1cAxlVIrhNe bTOZFU9SvF0IKSyttWSCPpirPBQbdKOLPAqz/Kd0vXkIByWAhsTfnxHQ94+KgBA7gwNq aFng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=QjnNslgNx3mbBBpZ7tPLJdkYzY7yWlZsdnOb9sU0rZk=; b=UJlLxSzgHXA8Lr4Umhoa0fO3ljjGEH+lcMkGbTmxN5+kqYU9kCVOxqOPOmS+JHuM89 6JtdV3sg2MGNFDxVqcNJ/WsHBpHSD+mTFsDWMKvwEUPZjBRgfONMgy7pWH6XApRFYDf2 Y2Zxz3NOvisxL/ni6r4M3BdD/Y8ktL5BnZE5myeNmBVjKnpJg6oXjTHTctYJ5A/pZ9Kf akSn/TZUMd0j6POsQKWvjEKKGQMWnMq75KCs9a29ve+VTwm/SFhGk2HF4ZcUIufh+Hic f+n9ZwQ4z3K5szUzxqSh2+XfvqS2BbfDsJovEe1kgEsW9X4eQd7LZRf/oIRFLZynI0Z8 aAXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Z5BA5dVv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id fl21si333089ejc.443.2021.06.08.11.05.13; Tue, 08 Jun 2021 11:05:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Z5BA5dVv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233986AbhFHSFZ (ORCPT + 99 others); Tue, 8 Jun 2021 14:05:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50628 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232789AbhFHSFX (ORCPT ); Tue, 8 Jun 2021 14:05:23 -0400 Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2099EC061574; Tue, 8 Jun 2021 11:03:14 -0700 (PDT) Received: by mail-ed1-x535.google.com with SMTP id i13so25599733edb.9; Tue, 08 Jun 2021 11:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QjnNslgNx3mbBBpZ7tPLJdkYzY7yWlZsdnOb9sU0rZk=; b=Z5BA5dVvOeOBDzMXCAxWXEc+NWYSgTtm4S1bf/juqcY9bkINKp7crZTkVYAsYZPJSJ srL1wWOA17cJJZr9GiKMfm0MtUEQt+6tgyGV0iQyK4aV5FQdNeBz07b9nZxvc9JqyZsK iIPtTlu5ufx4lWuNEwrSPY536Gh6SM8AzB0UAYCLYT/AyxWOdlpX11lykBFiBqy7Kv1b yiwiHWeTjJvvnEPD+pH4GeNV+Yj7r4DWgZfg7y2YCRL1L+R+3CCNnFq9KQLr935YA+AZ gxnqxO6crmoH4kUWKpMID4kFEj5f7NrFY/XIsTJkRwyDgNxLfs1VyJEzH+mMj49hwfzt s67w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QjnNslgNx3mbBBpZ7tPLJdkYzY7yWlZsdnOb9sU0rZk=; b=mS5OdB65VdsPQNnGCye3ngDt4tlSxsI+OQ8nTpfLqDz0XmA2kpQufj/0pRC4m1KsPG FT2/c0T+Qx3dAcvVlVQElQnZWbTVCI4GEBMG+HSL3tNrIPlNMBPec3Q4yNCARzSLVAS7 VNdtZYpWAHHGBdwhA68NF+IkrO8V5qQcQj4HdIITLPmvhcN0pGmBYZ8p62RLfqLGpdjK PdjRqbPKee3vBvyaPwaw/7hd8ki4onx+Uo2X7HvgGq853h5K+xrHkjVXiErqZi5hGhkw QbgC4qqRqBjazPK8Ywdb2kignPs0IQ5+/kWTeThRjGOik7mpayFfKxf2D0T9eaOzjy4N 4zVw== X-Gm-Message-State: AOAM530axET8glc90x93pSHaa73EYsioNzTVGsv4bBE1Ino5spSw6Svx uRabqdp8XvNs/4ZP/mWfrNVqinDrRNJfvA== X-Received: by 2002:a50:eb08:: with SMTP id y8mr27289378edp.89.1623175392538; Tue, 08 Jun 2021 11:03:12 -0700 (PDT) Received: from [192.168.2.2] (81-204-249-205.fixed.kpn.net. [81.204.249.205]) by smtp.gmail.com with ESMTPSA id d24sm170690edr.95.2021.06.08.11.03.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Jun 2021 11:03:12 -0700 (PDT) Subject: Re: [PATCH v6 1/8] dt-bindings: rockchip-sfc: Bindings for Rockchip serial flash controller To: Jon Lin , linux-spi@vger.kernel.org Cc: broonie@kernel.org, robh+dt@kernel.org, heiko@sntech.de, hjc@rock-chips.com, yifeng.zhao@rock-chips.com, sugar.zhang@rock-chips.com, linux-rockchip@lists.infradead.org, linux-mtd@lists.infradead.org, p.yadav@ti.com, macroalpha82@gmail.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Chris Morgan References: <20210608022644.21074-1-jon.lin@rock-chips.com> <20210608022644.21074-2-jon.lin@rock-chips.com> From: Johan Jonker Message-ID: Date: Tue, 8 Jun 2021 20:03:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: <20210608022644.21074-2-jon.lin@rock-chips.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jon, A look at the build log shows this error: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20210608022644.21074-2-jon.lin@rock-chips.com/ dtschema/dtc warnings/errors: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spi/rockchip-sfc.example.dt.yaml: spi@ff3a0000: clock-names:0: 'hclk_sfc' was expected From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spi/rockchip-sfc.yaml /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spi/rockchip-sfc.example.dt.yaml: spi@ff3a0000: clock-names:1: 'clk_sfc' was expected From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spi/rockchip-sfc.yaml Check document with: make ARCH=arm dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/spi/rockchip-sfc.yaml make ARCH=arm dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/spi/rockchip-sfc.yaml make ARCH=arm64 dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/spi/rockchip-sfc.yaml Remove any errors before submitting. === Johan On 6/8/21 4:26 AM, Jon Lin wrote: > From: Chris Morgan > > Add bindings for the Rockchip serial flash controller. New device > specific parameter of rockchip,sfc-no-dma included in documentation. > > Signed-off-by: Chris Morgan > Signed-off-by: Jon Lin > --- > > Changes in v6: > - Add support in device trees for rv1126(Declared in series 5 but not > submitted) > - Change to use "clk_sfc" "hclk_sfc" as clock lable, since it does not > affect interpretation and has been widely used > - Support sfc tx_dual, tx_quad(Declared in series 5 but not submitted) > - Simplify the code, such as remove "rockchip_sfc_register_all"(Declared > in series 5 but not submitted) > - Support SFC ver4 ver5(Declared in series 5 but not submitted) > - Add author Chris Morgan and Jon Lin to spi-rockchip-sfc.c > - Change to use devm_spi_alloc_master and spi_unregister_master > > Changes in v5: > - Add support in device trees for rv1126 > - Support sfc tx_dual, tx_quad > - Simplify the code, such as remove "rockchip_sfc_register_all" > - Support SFC ver4 ver5 > > Changes in v4: > - Changing patch back to an "RFC". An engineer from Rockchip > reached out to me to let me know they are working on this patch for > upstream, I am submitting this v4 for the community to see however > I expect Jon Lin (jon.lin@rock-chips.com) will submit new patches > soon and these are the ones we should pursue for mainlining. Jon's > patch series should include support for more hardware than this > series. > - Clean up documentation more and ensure it is correct per > make dt_binding_check. > - Add support in device trees for rk3036, rk3308, and rv1108. > - Add ahb clock (hclk_sfc) support for rk3036. > - Change rockchip_sfc_wait_fifo_ready() to use a switch statement. > - Change IRQ code to only mark IRQ as handled if it handles the > specific IRQ (DMA transfer finish) it is supposed to handle. > > Changes in v3: > - Changed the name of the clocks to sfc/ahb (from clk-sfc/clk-hsfc). > - Changed the compatible string from rockchip,sfc to > rockchip,rk3036-sfc. A quick glance at the datasheets suggests this > driver should work for the PX30, RK180x, RK3036, RK312x, RK3308 and > RV1108 SoCs, and possibly more. However, I am currently only able > to test this on a PX30 (an RK3326). The technical reference manuals > appear to list the same registers for each device. > - Corrected devicetree documentation for formatting and to note these > changes. > - Replaced the maintainer with Heiko Stuebner and myself, as we will > take ownership of this going forward. > - Noted that the device (per the reference manual) supports 4 CS, but > I am only able to test a single CS (CS 0). > - Reordered patches to comply with upstream rules. > > Changes in v2: > - Reimplemented driver using spi-mem subsystem. > - Removed power management code as I couldn't get it working properly. > - Added device tree bindings for Odroid Go Advance. > > Changes in v1: > hanges made in this new series versus the v8 of the old series: > - Added function to read spi-rx-bus-width from device tree, in the > event that the SPI chip supports 4x mode but only has 2 pins > wired (such as the Odroid Go Advance). > - Changed device tree documentation from txt to yaml format. > - Made "reset" message a dev_dbg from a dev_info. > - Changed read and write fifo functions to remove redundant checks. > - Changed the write and read from relaxed to non-relaxed when > starting the DMA transfer or reading the DMA IRQ. > - Changed from dma_coerce_mask_and_coherent to just > dma_set_mask_and_coherent. > - Changed name of get_if_type to rockchip_sfc_get_if_type. > > .../devicetree/bindings/spi/rockchip-sfc.yaml | 87 +++++++++++++++++++ > 1 file changed, 87 insertions(+) > create mode 100644 Documentation/devicetree/bindings/spi/rockchip-sfc.yaml > > diff --git a/Documentation/devicetree/bindings/spi/rockchip-sfc.yaml b/Documentation/devicetree/bindings/spi/rockchip-sfc.yaml > new file mode 100644 > index 000000000000..160449713f97 > --- /dev/null > +++ b/Documentation/devicetree/bindings/spi/rockchip-sfc.yaml > @@ -0,0 +1,87 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/spi/rockchip-sfc.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Rockchip Serial Flash Controller (SFC) > + > +maintainers: > + - Heiko Stuebner > + - Chris Morgan In the driver spi-rockchip-sfc.c is used: Chris Morgan Maybe use a consistent email address? Also Hotmail does strange things to message-ID's and links/content inside patches. > + > +allOf: > + - $ref: spi-controller.yaml# > + > +properties: > + compatible: > + oneOf: > + - const: rockchip,rk3036-sfc > + - items: > + - enum: > + - rockchip,px30-sfc > + - rockchip,rk3308-sfc > + - rockchip,rv1108-sfc > + - const: rockchip,rk3036-sfc > + - const: rockchip,rv1126-sfc A look at the driver shows this: +static const struct of_device_id rockchip_sfc_dt_ids[] = { + { .compatible = "rockchip,px30-sfc"}, remove + { .compatible = "rockchip,rk3036-sfc"}, + { .compatible = "rockchip,rk3308-sfc"}, + { .compatible = "rockchip,rv1126-sfc"}, remove + { /* sentinel */ } +}; When no '.data = &my_sfc_data' exist then there's no need for additional compatible strings in the driver. === example for I2S: { .compatible = "rockchip,rk3399-i2s", .data = &rk3399_i2s_pins }, === Compatibility strings are supposed to be SoC orientated. With rockchip_sfc_get_version() all we need is one fall back string for now I think. Is rk3568 identical. Please advise. - const: rockchip,rk3036-sfc - items: - enum: - rockchip,px30-sfc - rockchip,rk3308-sfc - rockchip,rk3368-sfc - rockchip,rk3568-sfc - rockchip,rv1108-sfc - rockchip,rv1126-sfc - const: rockchip,rk3036-sfc === The rk3368 TRM also describes a SFC controller. For the mainline DT completeness is it possible to add a rk3368 SFC node as well? ;) > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + clocks: > + items: > + - description: Bus Clock > + - description: Module Clock > + > + clock-names: > + items: > + - const: hclk_sfc > + - const: clk_sfc > + > + power-domains: > + maxItems: 1 > + > + rockchip,sfc-no-dma: > + description: Disable DMA and utilize FIFO mode only > + type: boolean > + > +required: > + - compatible > + - reg > + - interrupts > + - clocks > + - clock-names > + > +unevaluatedProperties: false > + > +examples: > + - | > + #include > + #include > + #include > + > + sfc: spi@ff3a0000 { > + compatible = "rockchip,px30-sfc","rockchip,rk3036-sfc"; > + reg = <0xff3a0000 0x4000>; > + interrupts = ; > + clocks = <&cru SCLK_SFC>, <&cru HCLK_SFC>; > + clock-names = "clk_sfc", "hclk_sfc"; The clocks in the examples and dtsi files must have the same sort order. > + pinctrl-0 = <&sfc_clk &sfc_cs &sfc_bus2>; > + pinctrl-names = "default"; > + power-domains = <&power PX30_PD_MMC_NAND>; > + #address-cells = <1>; > + #size-cells = <0>; > + > + flash@0 { From spi-controller.yaml: patternProperties: "^.*@[0-9a-f]+$": type: object properties: compatible: description: Compatible of the SPI device. reg: minimum: 0 maximum: 256 description: Chip select used by the device. This allows 257 sub nodes. Support up to 4 chip select in the driver. #define SFC_MAX_CHIPSELECT_NUM 4 > + compatible = "jedec,spi-nor"; > + reg = <0>; > + spi-max-frequency = <108000000>; > + spi-rx-bus-width = <2>; > + spi-tx-bus-width = <2>; > + }; > + }; > + > +... >