All of lore.kernel.org
 help / color / mirror / Atom feed
From: ijc@hellion.org.uk (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: Autoloading of SPI/nor driver on kirkwood (qnap devices)
Date: Tue, 02 Sep 2014 16:54:59 +0100	[thread overview]
Message-ID: <1409673299.14324.43.camel@dagon.hellion.org.uk> (raw)

Hello,

I recently tried to switch to using the DT based kirkwood stuff with
v3.16.1 on a QNAP TS-419 for the Debian kernel. Most things seemed ok
except that the flash driver was not autoloaded -- as well as spi-nor.ko
I had to manually modprobe m25p80.ko. Once I loaded both the flash was
detected.

I noticed that many platforms declare the flash chip as compatible =
"st,m25pXXX" whereas the ts219.dtsi just said m25p128 but I tried
changing that and it didn't help. In any case without spi-nor.ko being
autoloaded I don't support m25p80.ko ever would be.

I could set these things to =m for the Debian kirkwood flavour, but
since this is supposed to be a distro-style kernel.

I'm not entirely sure how module loading of this SPI stuff is supposed
to fit together -- anyone got any hints?

Ian.

             reply	other threads:[~2014-09-02 15:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 15:54 Ian Campbell [this message]
2014-09-02 17:06 ` Autoloading of SPI/nor driver on kirkwood (qnap devices) Ian Campbell
     [not found] ` <1409673299.14324.43.camel-ztPmHsLffjjnO4AKDKe2m+kiAK3p4hvP@public.gmane.org>
2014-09-04  2:11   ` Ben Hutchings
2014-09-04  2:11     ` Ben Hutchings
2014-09-04  2:11     ` Ben Hutchings
     [not found]     ` <1409796689.27524.34.camel-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2014-09-04  7:02       ` Geert Uytterhoeven
2014-09-04  7:02         ` Geert Uytterhoeven
2014-09-04  7:02         ` Geert Uytterhoeven
     [not found]         ` <CAMuHMdWBr=B0_Xivti9K5ReryHHEunQj2P26FjhmzhO-L9t+9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10  6:00           ` Brian Norris
2014-09-10  6:00             ` Brian Norris
2014-09-10  6:00             ` Brian Norris
2014-09-10  6:11             ` Brian Norris
2014-09-10  6:11               ` Brian Norris
2014-09-10  6:11               ` Brian Norris
     [not found]               ` <CAN8TOE_BRyg=Ww0oOxGeRr5Xkwh5hTq0UKQAR2dFjRVfwcBZoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10  7:59                 ` Geert Uytterhoeven
2014-09-10  7:59                   ` Geert Uytterhoeven
2014-09-10  7:59                   ` Geert Uytterhoeven
2014-09-14  2:00             ` Ben Hutchings
2014-09-14  2:00               ` Ben Hutchings
2014-09-14  2:00               ` Ben Hutchings
2014-09-04  2:21   ` Ben Hutchings
2014-09-04  2:21     ` Ben Hutchings
2014-09-04  2:21     ` Ben Hutchings

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=1409673299.14324.43.camel@dagon.hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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.