From: "Nick Burkitt" <nick.burkitt@nanotok.com>
To: linux-iio@vger.kernel.org
Subject: IIO driver module doesn't load automatically on kernel 4.19
Date: Wed, 29 Jan 2020 20:25:28 +0000 [thread overview]
Message-ID: <em32a58ce6-ecc9-4a0a-b47d-5d9b79f9bcc1@nanotok> (raw)
Hi All.
Pardon me if I'm in the wrong place, but I have to start somewhere.
I'm using an IIO driver (based on the BNO055 driver proposed by Vlad
Dogaru back in 2016).
All was well for a couple of years, but after I updated my kernel from
4.14 to 4.19, my driver will no longer load on boot, but is still happy
to be loaded manually with modprobe.
All other drivers load normally.
Has something changed in the way IIO drivers register themselves? Or has
some other requirement been added since 4.14 that I have to add to my
driver?
If not, any suggestions on where to go next would be appreciated.
Details:
Xilinx Zynq-7000 (ARM Cortex-A9, 2 cores@866 MHz), 1 GB RAM
Linux v4.19.0 (via Xilinx)
Ubuntu 16.04 and 18.04 (both exhibit the same problem)
Thanks,
-Nick
next reply other threads:[~2020-01-29 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 20:25 Nick Burkitt [this message]
2020-01-30 20:44 ` IIO driver module doesn't load automatically on kernel 4.19 Lars-Peter Clausen
2020-01-31 16:46 ` Re[2]: " Nick Burkitt
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=em32a58ce6-ecc9-4a0a-b47d-5d9b79f9bcc1@nanotok \
--to=nick.burkitt@nanotok.com \
--cc=linux-iio@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 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).