All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Klaus Kudielka <klaus.kudielka@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] SPI updates for v6.8
Date: Mon, 22 Jan 2024 18:35:13 +0000	[thread overview]
Message-ID: <be96e4bc-0a4d-444c-88cf-fc77fefd64fd@sirena.org.uk> (raw)
In-Reply-To: <d8724cd416494bb5cd5b0350266fce0cb7b3b210.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On Mon, Jan 22, 2024 at 07:30:09PM +0100, Klaus Kudielka wrote:
> On Sun, 2024-01-07 at 22:38 +0000, Mark Brown wrote:

> >  - Support for multiple chip selects.

> [skipped the rest]
> 
> Hi, it seems I have an issue related with this new feature.
> 
> I just booted 6.8.0-rc1 on Turris Omnia (CONFIG_SPI_ORION=y,
> device tree: arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts)

> and got the following error:
> 
> [    0.090231] spi_master spi0: No. of CS is more than max. no. of supported CS
> [    0.097358] spi_master spi0: Failed to create SPI device for /soc/spi@10600/flash@0

> End result: the three MTD partitions I used to have on the SPI-NOR are gone.

Yes, this was found on another platform - there's a patch which should
address this (unless the number is more than 8) in CI:

   https://lore.kernel.org/linux-spi/20240122-spi-multi-cs-max-v1-1-a7e98cd5f6c7@kernel.org/T/#u

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-01-22 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 22:38 [GIT PULL] SPI updates for v6.8 Mark Brown
2024-01-09 23:41 ` pr-tracker-bot
2024-01-22 18:30 ` Klaus Kudielka
2024-01-22 18:35   ` Mark Brown [this message]
2024-01-22 18:38   ` Mark Brown
2024-01-22 18:57     ` Klaus Kudielka
2024-01-22 19:24       ` Mark Brown
2024-01-23 19:57     ` Klaus Kudielka

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=be96e4bc-0a4d-444c-88cf-fc77fefd64fd@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=klaus.kudielka@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /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.