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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 71483C433EF for ; Fri, 4 Feb 2022 22:15:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346815AbiBDWPY (ORCPT ); Fri, 4 Feb 2022 17:15:24 -0500 Received: from mail-ot1-f47.google.com ([209.85.210.47]:46614 "EHLO mail-ot1-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346848AbiBDWPX (ORCPT ); Fri, 4 Feb 2022 17:15:23 -0500 Received: by mail-ot1-f47.google.com with SMTP id l12-20020a0568302b0c00b005a4856ff4ceso6100810otv.13; Fri, 04 Feb 2022 14:15:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=N8RFHngLhDeWO4wQPXHQGcIdh24A8gAlUMWTLplW+TI=; b=iYoKOD7LQyRzvMDM8duQPme7Oa96o2IjRLv8UmAWlGBjYnnMruE/HxIANiOuFH+Fby dKjkg6VlDFQLJeoNv1Otr44yB21PRs27NlTVMZASA4dFClRGf6QK77x/VXVdbbujwPdU tsZ9vjYiiH6WyM8phvD+9sOnGorEX9JlYludRmrq91kb4UCr+Awzd/HtGKXNuNjtIyRK Ac1XW9hS8AeZJ83MX7/vIlDsdO92f3gwRYSj9FF9t2rGDu1yryj0/sGQkrk22eC8BECN iQb/RuGfLsk36kATp65HUA4a16jnmbmELkwQjvqv5YNg2q4d/irFuJYNmclLYM3ItfY1 z/8Q== X-Gm-Message-State: AOAM532Cy9+AXvbKqkI9db/cG7dCmR1jBPiuYEoYT7RyzVvRyaA7cgi7 YofKNH9YioVFdiWI7dLISpztimM+iw== X-Google-Smtp-Source: ABdhPJw1r36BfQdNmjT2kjJd0xyM5pbLBON8ItumuXjTSCU4U75vKCiZ0SQbcnm/cAX7aMItBNevWw== X-Received: by 2002:a9d:4e03:: with SMTP id p3mr403290otf.299.1644012922815; Fri, 04 Feb 2022 14:15:22 -0800 (PST) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id 31sm1243392otr.13.2022.02.04.14.15.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 04 Feb 2022 14:15:22 -0800 (PST) Received: (nullmailer pid 3277483 invoked by uid 1000); Fri, 04 Feb 2022 22:15:20 -0000 Date: Fri, 4 Feb 2022 16:15:20 -0600 From: Rob Herring To: Krzysztof Kozlowski Cc: linux-samsung-soc@vger.kernel.org, Guenter Roeck , Benson Leung , Lee Jones , Rob Herring , Pratyush Yadav , Mark Brown , linux-kernel@vger.kernel.org, Andi Shyti , devicetree@vger.kernel.org, Alim Akhtar , Sam Protsenko , linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v6 1/4] spi: dt-bindings: samsung: convert to dtschema Message-ID: References: <20220124082347.32747-1-krzysztof.kozlowski@canonical.com> <20220124082347.32747-2-krzysztof.kozlowski@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220124082347.32747-2-krzysztof.kozlowski@canonical.com> Precedence: bulk List-ID: X-Mailing-List: linux-spi@vger.kernel.org On Mon, 24 Jan 2022 09:23:44 +0100, Krzysztof Kozlowski wrote: > Convert the Samsung SoC (S3C24xx, S3C64xx, S5Pv210, Exynos) SPI > controller bindings to DT schema format. > > The conversion also drops requirement from providing controller-data and > its data for each of SPI peripheral device nodes. The dtschema cannot > express this and the requirement is being relaxed in the driver now. > > Signed-off-by: Krzysztof Kozlowski > Reviewed-by: Sam Protsenko > Acked-by: Pratyush Yadav > --- > .../bindings/soc/samsung/exynos-usi.yaml | 2 +- > .../spi/samsung,spi-peripheral-props.yaml | 33 ++++ > .../devicetree/bindings/spi/samsung,spi.yaml | 187 ++++++++++++++++++ > .../bindings/spi/spi-peripheral-props.yaml | 1 + > .../devicetree/bindings/spi/spi-samsung.txt | 122 ------------ > MAINTAINERS | 2 +- > 6 files changed, 223 insertions(+), 124 deletions(-) > create mode 100644 Documentation/devicetree/bindings/spi/samsung,spi-peripheral-props.yaml > create mode 100644 Documentation/devicetree/bindings/spi/samsung,spi.yaml > delete mode 100644 Documentation/devicetree/bindings/spi/spi-samsung.txt > Reviewed-by: Rob Herring