From: Colin Foster <colin.foster@in-advantage.com>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>
Subject: 6.8 SPI Chip Select Regression
Date: Tue, 2 Apr 2024 16:32:50 -0500 [thread overview]
Message-ID: <Zgx5glZznSCheksj@euler> (raw)
Hi Amit,
I finally got around to testing 6.9-rc2. I must've missed testing
6.8, however, because it seems there are issues - at least in my device
tree - with commit: 4d8ff6b0991d "spi: Add multi-cs memories support in SPI core"
I'm running on a BeagleBone Black, and have a single MFD attached to CS
0. At boot, I see the following:
[ 3.459990] omap2_mcspi 48030000.spi: chipselect 0 already in use
[ 3.466135] spi_master spi0: spi_device register error /ocp/interconnect@48000000/segment@0/target-module@30000/spi@0/soc@0
[ 3.477495] spi_master spi0: Failed to create SPI device for /ocp/interconnect@48000000/segment@0/target-module@30000/spi@0/soc@0
Is this a known issue? Is there anything I either might need to do to a
device tree, or something you might suggest to help troubleshoot this?
Hardware name: Generic AM33XX (Flattened Device Tree)
Workqueue: events_unbound deferred_probe_work_func
Backtrace:
dump_backtrace from show_stack+0x20/0x24
show_stack from dump_stack_lvl+0x60/0x78
dump_stack_lvl from dump_stack+0x18/0x1c
dump_stack from __spi_add_device+0x190/0x224
__spi_add_device from spi_add_device+0x50/0x64
spi_add_device from of_register_spi_device+0x3d4/0x594
of_register_spi_device from spi_register_controller+0x3b0/0x6b8
spi_register_controller from devm_spi_register_controller+0x54/0x94
devm_spi_register_controller from omap2_mcspi_probe+0x4c4/0x584
omap2_mcspi_probe from platform_probe+0x6c/0xcc
platform_probe from really_probe+0xd8/0x2e8
Thank you.
Colin Foster
next reply other threads:[~2024-04-02 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 21:32 Colin Foster [this message]
2024-04-02 23:52 ` 6.8 SPI Chip Select Regression Mark Brown
2024-04-03 2:14 ` Colin Foster
2024-04-03 21:24 ` Andy Shevchenko
2024-04-11 16:02 ` Colin Foster
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=Zgx5glZznSCheksj@euler \
--to=colin.foster@in-advantage.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=broonie@kernel.org \
--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.