All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] spi: sh-msiof: drop support for R-Car H3 ES1.[01]
Date: Mon, 23 Jan 2023 10:42:52 +0100	[thread overview]
Message-ID: <CAMuHMdX072wWj=h48oVe47bkaw144HmMeq2bNbiE+ZUMhz56eA@mail.gmail.com> (raw)
In-Reply-To: <20230123075833.50925-1-wsa+renesas@sang-engineering.com>

Hi Wolfram,

On Mon, Jan 23, 2023 at 8:58 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> These revisions have HW issues and are only early engineering samples
> used internally. We simply drop the MSIOF support for them.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> We got confirmation from Renesas for dropping ES1.* support.

Thanks for your patch!

> --- a/drivers/spi/spi-sh-msiof.c
> +++ b/drivers/spi/spi-sh-msiof.c
> @@ -24,6 +24,7 @@
>  #include <linux/platform_device.h>
>  #include <linux/pm_runtime.h>
>  #include <linux/sh_dma.h>
> +#include <linux/sys_soc.h>
>
>  #include <linux/spi/sh_msiof.h>
>  #include <linux/spi/spi.h>
> @@ -1257,8 +1258,15 @@ static void sh_msiof_release_dma(struct sh_msiof_spi_priv *p)
>         dma_release_channel(ctlr->dma_tx);
>  }
>
> +static const struct soc_device_attribute sh_msiof_blacklist[] = {
> +       /* Those have HW issues */
> +       { .soc_id = "r8a7795", .revision = "ES1.[01]" },
> +       { /* Sentinel */ }
> +};
> +
>  static int sh_msiof_spi_probe(struct platform_device *pdev)
>  {
> +       const struct soc_device_attribute *attr;
>         struct spi_controller *ctlr;
>         const struct sh_msiof_chipdata *chipdata;
>         struct sh_msiof_spi_info *info;
> @@ -1267,6 +1275,10 @@ static int sh_msiof_spi_probe(struct platform_device *pdev)
>         int i;
>         int ret;
>
> +       attr = soc_device_match(sh_msiof_blacklist);
> +       if (attr)
> +               return -ENOTSUPP;

I don't think adding more soc_device_match() calls is the proper way to
handle this...
What about adding a single check to drivers/soc/renesas/renesas-soc.c,
removing r8a77950*dts*, and removing all R-Car H3 ES1.x matches from
all drivers?

> +
>         chipdata = of_device_get_match_data(&pdev->dev);
>         if (chipdata) {
>                 info = sh_msiof_spi_parse_dt(&pdev->dev);

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2023-01-23  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  7:58 [PATCH] spi: sh-msiof: drop support for R-Car H3 ES1.[01] Wolfram Sang
2023-01-23  9:42 ` Geert Uytterhoeven [this message]
2023-01-23 10:02   ` Wolfram Sang
2023-01-25 13:39     ` Wolfram Sang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMuHMdX072wWj=h48oVe47bkaw144HmMeq2bNbiE+ZUMhz56eA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.