Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32;
Date:   Wed, 27 Sep 2023 11:00:12 +0200
From:   Mark Brown <broonie@kernel.org>
To:     Geert Uytterhoeven <geert@linux-m68k.org>
Cc:     Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Magnus Damm <magnus.damm@gmail.com>, linux-spi@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-renesas-soc@vger.kernel.org,
        Chris Paterson <Chris.Paterson2@renesas.com>,
        Biju Das <biju.das@bp.renesas.com>,
        Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 1/2] spi: renesas,rzv2m-csi: Add SPI Slave related
 properties
Message-ID: <ZRPvHJXbuZ9Db2Go@finisterre.sirena.org.uk>
References: <20230926210818.197356-1-fabrizio.castro.jz@renesas.com>
 <20230926210818.197356-2-fabrizio.castro.jz@renesas.com>
 <CAMuHMdUibHxPBCLbeWdNrEk_szm+o4cOcskEMZAqUufNTzQKMQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="QiSZLj8ULhE5uAOG"
Content-Disposition: inline
In-Reply-To: <CAMuHMdUibHxPBCLbeWdNrEk_szm+o4cOcskEMZAqUufNTzQKMQ@mail.gmail.com>
Precedence: bulk


--QiSZLj8ULhE5uAOG
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 27, 2023 at 09:59:05AM +0200, Geert Uytterhoeven wrote:
> On Tue, Sep 26, 2023 at 11:08=E2=80=AFPM Fabrizio Castro

> > +    type: boolean
> > +    description:
> > +      Use CSI Slave Selection (SS) pin to enable transmission and rece=
ption when
> > +      in slave mode.

> Can't this be done in a more generic way? I had expected that the
> existing SPI_NO_CS flag can be set using a property in the "slave" subnod=
e,
> but apparently there is no "spi-no-cs" property defined yet.

The description is clearly saying there is a chip select, _NO_CS seems
entirely inappropriate.  It's not specified in the device tree because
when there's no chip select for a device it's a fundamental property of
how the device is controlled and we don't need any information beyond
the compatible.

--QiSZLj8ULhE5uAOG
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmUT7xsACgkQJNaLcl1U
h9Cv4Qf/XYUHiyb3CeUAVkgA5kzU23PQo4xps4f/9NjXmDxMNXGjd1mJz9drxsHP
orKXtyGMHXzQH+Md2RB4J7NMy+6W9wNCugC9rM11EClpnnSCvbqOMiybxgmW3kwa
nCpefQU+RK6Glv+wL1wNrKEJIWHKjefkFTODIJb2mxQ3QRhTBoOQcT1r0VZHJiTP
x5F44Hjq8apm/HBve10boE2dk+9NeRN7rKvT0HRaCSU0nN4tBtICJbYZjj++2o0b
6GHQCti/Dp+JahGpi4Q1MbUmS4XsZ33+pvXcxuFmkrJy/EkfzRTs0+5mYAcqM5x/
HN+l2oJlUTEqr+jp38Aqxdm9doYEtg==
=VLyd
-----END PGP SIGNATURE-----

--QiSZLj8ULhE5uAOG--