public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	ldewangan@nvidia.com, thierry.reding@gmail.com,
	jonathanh@nvidia.com, linux-spi@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: Re: [regression] jetson-tk1: spi do not probe anymore
Date: Mon, 5 May 2025 10:54:55 +0200	[thread overview]
Message-ID: <aBh839v-3Z1ReDi4@Red> (raw)
In-Reply-To: <CALHNRZ-At4WmJXoNs_x0XD=bRTRsKMBm1qOQGkFcNOvFfVDaMw@mail.gmail.com>

Le Sun, May 04, 2025 at 09:10:59PM -0500, Aaron Kling a écrit :
> On Sun, May 4, 2025 at 5:37 PM Mark Brown <broonie@kernel.org> wrote:
> >
> > On Sun, May 04, 2025 at 01:23:29PM +0200, Corentin Labbe wrote:
> >
> > > On my jetson-tk1, SPI do not probe anymore:
> > > [    1.330681] spi spi1.0: Invalid delay unit 2, should be SPI_DELAY_UNIT_SCK
> > > [    1.335185] spi-tegra114 7000da00.spi: can't setup spi1.0, status -22
> > > [    1.341643] spi_master spi1: spi_device register error /spi@7000da00/flash@0
> > > [    1.348637] spi_master spi1: Failed to create SPI device for /spi@7000da00/flash@0
> > > I tested 6.14.7
> > > The SPI probed perfectly in 4.17.14
> >
> > That's a pretty big jump in versions...
> >
> > > I tried to debug a bit, and the driver requires units to be SPI_DELAY_UNIT_SCK, but it seems there is no way to set it.
> > > Removing the "return -EINVAL" in tegra_spi_set_hw_cs_timing() lead to a successfull probe and the flash device appear.
> > > But I agree, it is not a correct fix:)
> > >
> > > Since only the test made it fail, I think the driver is bad since commit 810593668468 ("spi: tegra114: change format for `spi_set_cs_timing()` function")
> >
> > Adding Alexandru who wrote that commit.  Assuming the delays came from
> > DT (I'm not actually finding them, I didn't look too hard though) and
> > are therefore in units of wall clock time I think we need to add a
> > conversion helper for the units which the driver can use to convert to
> > whatever units it actually wants to use, we do need to accept units of
> > wall clock time given the generic binding there.  That gets a bit
> > annoying if the bus speed changes, though that's quite infrequent in
> > practice.
> 
> This should be fixed by a patch [0] which was recently picked up. I
> saw the same issue on a tegra 210 device and submitted that to fix it.
> Can you verify if it fixes this case too?
> 
> Sincerely,
> Aaron
> 
> [0] https://lore.kernel.org/all/20250423-spi-tegra114-v1-1-2d608bcc12f9@gmail.com/

Yes it fixes my case

Thanks
Regards

  reply	other threads:[~2025-05-05  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 11:23 [regression] jetson-tk1: spi do not probe anymore Corentin Labbe
2025-05-04 22:37 ` Mark Brown
2025-05-05  2:10   ` Aaron Kling
2025-05-05  8:54     ` Corentin Labbe [this message]
2025-05-05 10:28     ` Mark Brown

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=aBh839v-3Z1ReDi4@Red \
    --to=clabbe.montjoie@gmail.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=webgeek1234@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox