Received: by 2002:a05:7412:98c1:b0:fa:551:50a7 with SMTP id kc1csp1306847rdb; Sun, 7 Jan 2024 13:27:21 -0800 (PST) X-Google-Smtp-Source: AGHT+IEP7pDbTJ7ErgEZWO6rRJ85gXK8ixzP4NoIDYm99vwdSChyA5UIqNdF8bbHVZ7cbm0aEkbA X-Received: by 2002:a05:6e02:1523:b0:360:74af:d9a0 with SMTP id i3-20020a056e02152300b0036074afd9a0mr4610580ilu.39.1704662840930; Sun, 07 Jan 2024 13:27:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704662840; cv=none; d=google.com; s=arc-20160816; b=T1ejbtzmlccRPbdOqj6U44NytJQ53dQYCAFFhe0cS8B5LHK/20MNvK3gQMPhFM54C/ AeTxY4gA8f8G6DPT6cYZDjABZwJWg25uLQxMto5TnE1SQ2E84lB9vwidYcTgJ7840Y3q +BNCkpupiensNXAUWSZTSOto07wal5VRPIHrfDqFtNVuZH2Dc983scBf54ca56nBlrQH zR1PebWE58dQMmbikPJrM0C1jEt4rghV0+2yiObVKFgWU04Wh1aruUemanILqMSnmFHc bvL0pGMPA8OyS4Oes+GmeZMN4XxFr8rp05azp2/4FUAwVg1IkDVYnXaBXsKGsxNboYrj Tt1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=cyqvQ4HMKpa2kInRoWExv2gVRPwMWUcDdTS0GISW7wc=; fh=NQeEq3Vi3RKqYE7Q8kjWogqHYgP43C3izwdDRTL/How=; b=XVWNNPOqmC4YQ09HhfFBILSDvCKoXxpojXiTIND4SxuM36zOm0r9o6l0+J/eZQ48kl /kv4hq8KsxfvLndp4bohJOVBkbZ5bcH0IsA7fhzmHQCzw6NZ84OGk+b6mw+/7IUqGZ1L GLbmBsyEFinbCZB7GM1vluS4E5OqjVa9Zbj+ZWnFVtpePd68n4fBNQWKY3N0gxkGbs/i rxFkCAL3tGzoT4l7QKGx8LtJ7dU6iVh4ZLEzm5cfNRwfZ+95vxG4WFmQdPvqqim7X2zB Dx0YGL39tGSw5hC6Bb0NmYBDp5cR8GzDfgjyKaqUbdDsDBGBXIjBjeXJu5MRzRFt6pVw swHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=PPvA+OiD; spf=pass (google.com: domain of linux-kernel+bounces-18989-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-18989-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [2604:1380:40f1:3f00::1]) by mx.google.com with ESMTPS id bb5-20020a170902bc8500b001d4526d0037si4940227plb.170.2024.01.07.13.27.20 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 07 Jan 2024 13:27:20 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-18989-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=PPvA+OiD; spf=pass (google.com: domain of linux-kernel+bounces-18989-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-18989-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 sy.mirrors.kernel.org (Postfix) with ESMTPS id CCBFBB210FA for ; Sun, 7 Jan 2024 21:27:16 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D7A8911C92; Sun, 7 Jan 2024 21:27:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="PPvA+OiD" X-Original-To: linux-kernel@vger.kernel.org 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 F18A01171F; Sun, 7 Jan 2024 21:27:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 152F2C433C8; Sun, 7 Jan 2024 21:27:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704662826; bh=aBmge42Re3CaD2B3sL9kHBYYzLg5qbRP+fss6SIm1vE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=PPvA+OiDFhYQ+cI7jhyBzzV2Kcq6SlxLq0AysKvsBVc+t8DLgjpYH4AwwLON8u8Te zjr3AkqX0/k57qyHPfXb7gprRCbJgQayyQ18iCHka6rKWvgc+qSaKabhwGVBfsdYq1 7erbgT2rnOlJe4zf3FA5zGAkIe56VDZG0xzfydyeAMfbcgvHySSAkNRvJoVKOqfK8Q NvMzEwS9whTwLha876tLcySWTkeelOIhmUICTaEU3UC6GYGKIx0TofWYcgVwHztpHV dFFubxov4QhIftjlBMCfo2yO3wqKl73goJG+p0PJs3PnCUj9YcAc4nl3olXQorMgCM 6lDrsHf3ynjLQ== Date: Sun, 7 Jan 2024 21:26:59 +0000 From: Mark Brown To: Jonathan Cameron Cc: David Lechner , linux-iio@vger.kernel.org, linux-spi@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring , Krzysztof Kozlowski , Conor Dooley , Michael Hennerich , Nuno =?iso-8859-1?Q?S=E1?= , Liam Girdwood , linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 1/3] dt-bindings: spi: add spi-rx-bus-channels peripheral property Message-ID: References: <20231215-ad7380-mainline-v3-0-7a11ebf642b9@baylibre.com> <20231215-ad7380-mainline-v3-1-7a11ebf642b9@baylibre.com> <20240107164356.3e8df266@jic23-huawei> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Fv0DJ3jRqIS10aZI" Content-Disposition: inline In-Reply-To: <20240107164356.3e8df266@jic23-huawei> X-Cookie: Love means nothing to a tennis player. --Fv0DJ3jRqIS10aZI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jan 07, 2024 at 04:43:56PM +0000, Jonathan Cameron wrote: > David Lechner wrote: > > This adds a new spi-rx-bus-channels property to the generic spi > > peripheral property bindings. This property is used to describe > > devices that have parallel data output channels. > > This property is different from spi-rx-bus-width in that the latter > > means that we are reading multiple bits of a single word at one time > > while the former means that we are reading single bits of multiple words > > at the same time. > Mark, could you take a look at this SPI binding change when you have time? Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone. > I don't want to apply it without your view on whether this makes sense > from a general SPI point of view as we all hate maintaining bindings > if they turn out to not be sufficiently future looking etc and we need > to deprecate them in favour of something else. This makes no sense to me without a corresponding change in the SPI core and possibly controller support, though I guess you could do data manging to rewrite from a normal parallel SPI to this for a pure software implementation. I also see nothing in the driver that even attempts to parse this so I can't see how it could possibly work. --Fv0DJ3jRqIS10aZI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmWbFyMACgkQJNaLcl1U h9AzYgf+Mbh0jgcqo96lL6XLC32m37OlYdd9fUKv0+KUOEXnZaUQ7qSCxWmhGgAP A2b1ghi/zUK7TsqVz8j+942keDay/MqUYOsrRMXpYpgELqWDlkLCh9TN/lpAbXJB q6dSJ7LnzJPH27JocTjnOFv16EILR/8974m14laHlQ49Rqr4egzfRNDHgfTyOFci DIsEp7kGIM3Xt1WeQzYlvxpDPeD4pRmlZBO6/zS9w77c4d+UXugNB/s1P/C5YNRK 8l9iTvCtcTjkgFuznUQZIqfYYZYLC00jcpt/MsDCLz+bY4lHQTsoZMuvdpAjMspW SzABJV2fJNW1ZG1pWTy3YNc54Em1IA== =jAw8 -----END PGP SIGNATURE----- --Fv0DJ3jRqIS10aZI--