From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Brown <broonie@kernel.org>,
kirill.kapranov@compulab.co.il,
linux-spi <linux-spi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -next: Traceback at at drivers/spi/spi.c:2179 spi_register_controller
Date: Mon, 27 Aug 2018 12:41:16 +0200 [thread overview]
Message-ID: <CAMuHMdUugeKbUgfKpwYCXQrpMys8hrWUXr0FZWAW7ryeZoS1dg@mail.gmail.com> (raw)
In-Reply-To: <20180823200834.GA9368@roeck-us.net>
Hi Guenter,
On Thu, Aug 23, 2018 at 10:08 PM Guenter Roeck <linux@roeck-us.net> wrote:
> I see the attached warning when booting 'sabrelite' images in qemu,
> using imx_v6_v7_defconfig and imx6dl-sabrelite.dts.
>
> Context suggests that the warning is seen since commit 1a4327fbf4554 ("spi:
> fix IDR collision on systems with both fixed and dynamic SPI bus numbers").
>
> Guenter
>
> ---
> [ 7.105230] ------------[ cut here ]------------
> [ 7.105509] WARNING: CPU: 0 PID: 1 at drivers/spi/spi.c:2179 spi_register_controller+0x7dc/0x938
> [ 7.105760] couldn't get idr
Correct, all SPI controllers instantiated from DT and using DT aliases
are broken.
https://lore.kernel.org/lkml/20180821095303.27664-1-geert+renesas@glider.be/
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
prev parent reply other threads:[~2018-08-27 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 20:08 -next: Traceback at at drivers/spi/spi.c:2179 spi_register_controller Guenter Roeck
2018-08-27 10:41 ` Geert Uytterhoeven [this message]
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=CAMuHMdUugeKbUgfKpwYCXQrpMys8hrWUXr0FZWAW7ryeZoS1dg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=kirill.kapranov@compulab.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).