Received-SPF: pass (google.com: domain of linux-kernel+bounces-55005-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Precedence: bulk
MIME-Version: 1.0
References: <20240205191808.998754-1-frut3k7@gmail.com> <ZcH9u7Vo2sFERIHJ@finisterre.sirena.org.uk>
In-Reply-To: <ZcH9u7Vo2sFERIHJ@finisterre.sirena.org.uk>
From: frut3k7 <frut3k7@gmail.com>
Date: Tue, 6 Feb 2024 14:16:47 +0100
Message-ID: <CAKEyCaBnxumU0otxbtzAqLqUN+n5+qwWuvfNGCJa=rCfzE=ibg@mail.gmail.com>
Subject: Re: [PATCH 1/2] spi: spidev: Add Qualcomm spidev device compatible
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 6, 2024 at 10:37=E2=80=AFAM Mark Brown <broonie@kernel.org> wro=
te:
>
> On Mon, Feb 05, 2024 at 08:18:05PM +0100, Pawe=C5=82 Owoc wrote:
> > Add compatible string for Qualcomm spidev device (used for QCA4024).
>
> > --- a/drivers/spi/spidev.c
> > +++ b/drivers/spi/spidev.c
> > @@ -710,6 +710,7 @@ static const struct spi_device_id spidev_spi_ids[] =
=3D {
> >       { .name =3D "spi-authenta" },
> >       { .name =3D "em3581" },
> >       { .name =3D "si3210" },
> > +     { .name =3D "spidev" },
> >       {},
>
> Why?
>
> >       { .compatible =3D "lwn,bk4", .data =3D &spidev_of_check },
> >       { .compatible =3D "menlo,m53cpld", .data =3D &spidev_of_check },
> >       { .compatible =3D "micron,spi-authenta", .data =3D &spidev_of_che=
ck },
> > +     { .compatible =3D "qca,spidev", .data =3D &spidev_of_check },
>
> No, this needs to correspond to the hardware being controlled via spidev
> not to an implementation detail.  Any new compatibles also need to be
> documented.


The device for which I want to add compatibility is originally used in
the router and this is what the dts fragment looks like:

    spi@78b8000 {
      #address-cells =3D <0x01>;
      #size-cells =3D <0x00>;
      clock-names =3D "core\0iface";
      clocks =3D <0x03 0x5c 0x03 0x54>;
      compatible =3D "qcom,spi-qup-v2.2.1";
      cs-select =3D <0x02>;
      dma-names =3D "tx\0rx";
      dmas =3D <0x06 0x12 0x06 0x13>;
      interrupts =3D <0x00 0x62 0x00>;
      pinctrl-0 =3D <0x08>;
      pinctrl-names =3D "default";
      quartz-reset-gpio =3D <0x09 0x15 0x01>;
      reg =3D <0x78b8000 0x600>;
      spi-max-frequency =3D <0x2faf080>;
      status =3D "ok";

      spi@3 {
        compatible =3D "qca,spidev";
        reg =3D <0x00>;
        spi-max-frequency =3D <0x16e3600>;
      };
    };

The first part has already been added:
https://lore.kernel.org/all/20231123121324.1046164-1-robimarko@gmail.com/

According to this commit, Qualcomm use this compatibility:
https://github.com/dissent1/msm-2/commit/d6160218393552fea1b7973787f2bd154f=
870ee2

>
> I'm also missing patch 2 of this series so don't know what's going on
> there.


The second patch was sent only to the devicetree bindings project:
https://lore.kernel.org/all/20240205191828.998783-1-frut3k7@gmail.com/
It's probably done wrong...