Received: by 2002:a05:7412:3b8b:b0:fc:a2b0:25d7 with SMTP id nd11csp2528189rdb; Mon, 12 Feb 2024 07:44:37 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCVO+79hPw5RQEbvpzYHPQSlTqCDIO0W5zj3KAns3NgsTaCbv4C1XS+bRn4SRXgJHXm4h6IJkPfQmQslLEbfU+UG2a1gpNdZOjRJkNLS3A== X-Google-Smtp-Source: AGHT+IEKfbNMrKZNwd8pxQQ0aKAc6XvoXkhQ1BvZUsrYxEmS5ghb58PvkYJaWbLrxUzEbz8n/xXM X-Received: by 2002:a17:90a:d503:b0:297:2132:982c with SMTP id t3-20020a17090ad50300b002972132982cmr3255249pju.43.1707752676787; Mon, 12 Feb 2024 07:44:36 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCWDAIy3uX7SeglLdn6HkFrCm6xCfFyYzGFSEy28M/vHeyUSucvSC0VNr2njeyNUGaAhd1qTNmrWXQin4BMIB9AX8KoFhmcXBdr8SIzWqQ== Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id lw1-20020a17090b180100b00297208169a9si470719pjb.30.2024.02.12.07.44.36 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Feb 2024 07:44:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-61907-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@kernel.org header.s=k20201202 header.b="N/dWWajb"; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-61907-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-61907-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 317302858F0 for ; Mon, 12 Feb 2024 15:36:10 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 50A713C68E; Mon, 12 Feb 2024 15:36:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="N/dWWajb" Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7412B12E52; Mon, 12 Feb 2024 15:36:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707752162; cv=none; b=briSRRigTR+upQ0gxfs4kDRd84wjGCi12aNOmu45VuUOopV1dt5dHNMdqVIgbVqxje0bQWhXJZYloaeKsVBRWvw5hl0UEDwVTBBJKg5CvRdG4dUWHBDB4W4qI4nISPViP4po2Q1A07/PcgsJd/YRI/V+ekntbbW9ebkJeX7KC+Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707752162; c=relaxed/simple; bh=OsnsW5WMX5bnFUSUa6rJ6/poLxq4vFG7wdQg2ic2Pu0=; h=Date:Content-Type:MIME-Version:From:To:Cc:In-Reply-To:References: Message-Id:Subject; b=W2XeTpBtiLI29EYUs674STltuOOjCkJUx49+KrcGC7SbEPzeehDfuyvkW+V31Vtkqj9jFPxvIRy55yMmxVYkL/KES9l1urb9VGTmW3okmeI6axgcC9CiHi0e07I16MtxSS6SbXmUSyEr3kBFHJPnLNQc01aYlLTSe9NphIA7n58= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=N/dWWajb; arc=none smtp.client-ip=10.30.226.201 Received: by smtp.kernel.org (Postfix) with ESMTPSA id C8C17C433F1; Mon, 12 Feb 2024 15:36:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1707752162; bh=OsnsW5WMX5bnFUSUa6rJ6/poLxq4vFG7wdQg2ic2Pu0=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=N/dWWajbDJ9QTuLpoEYTptaUAKUENXuJaUe3gpaNVcA6bsOGfLV/U22ZYa0f88SWj dYd2HHaE26EA2GfcfvV/0CSTnPsLrketIfchZ79AhNqvnGbTtkUR2fzcwalVW4J3AV /3FD0vn9/ArjW0o2rwzLgUMgViFTTSPPgj2j3YI69uVX/yXppOE81gI87WFUXz0TKH k90XarTGrdTq8VhQXB8dbyF3VpIo/yRrGbqUl4L7O7ryEONyLdUQmFbrqocjsyagsF Db3KRK/E8C782V5a/ByQD7efy4w3Y0YTfcSoLeOewM+VYURaZQ2VYSjonVWR0RixSF V6UGS5M7CX0wA== Date: Mon, 12 Feb 2024 09:36:00 -0600 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: Rob Herring To: Tudor Ambarus Cc: arnd@arndb.de, krzysztof.kozlowski@linaro.org, andre.draszik@linaro.org, willmcvicker@google.com, andi.shyti@kernel.org, alim.akhtar@samsung.com, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@android.com, linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org, linux-samsung-soc@vger.kernel.org, semen.protsenko@linaro.org, devicetree@vger.kernel.org, peter.griffin@linaro.org, broonie@kernel.org In-Reply-To: <20240212140331.915498-2-tudor.ambarus@linaro.org> References: <20240212140331.915498-1-tudor.ambarus@linaro.org> <20240212140331.915498-2-tudor.ambarus@linaro.org> Message-Id: <170775215967.605422.1424850912641172864.robh@kernel.org> Subject: Re: [PATCH v2 01/12] spi: dt-bindings: introduce FIFO depth properties On Mon, 12 Feb 2024 14:03:20 +0000, Tudor Ambarus wrote: > There are SPI IPs that can be configured by the integrator with a > specific FIFO depth depending on the system's capabilities. For example, > the samsung USI SPI IP can be configured by the integrator with a TX/RX > FIFO from 8 byte to 256 bytes. > > Introduce the ``fifo-depth`` property for such instances of IPs where the > same FIFO depth is used for both RX and TX. Introduce ``rx-fifo-depth`` > and ``tx-fifo-depth`` properties for cases where the RX FIFO depth is > different from the TX FIFO depth. > > Make the dedicated RX/TX properties dependent on each other and mutual > exclusive with the other. > > Signed-off-by: Tudor Ambarus > --- > .../bindings/spi/spi-controller.yaml | 27 +++++++++++++++++++ > 1 file changed, 27 insertions(+) > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: /Documentation/devicetree/bindings/spi/spi-controller.yaml:152:9: [warning] wrong indentation: expected 6 but found 8 (indentation) /Documentation/devicetree/bindings/spi/spi-controller.yaml:156:9: [warning] wrong indentation: expected 6 but found 8 (indentation) dtschema/dtc warnings/errors: doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240212140331.915498-2-tudor.ambarus@linaro.org The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.