From: Grant Likely <grant.likely@secretlab.ca>
To: Tomoya MORINAGA <morinaga526@dsn.okisemi.com>
Cc: 'David Brownell' <dbrownell@users.sourceforge.net>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org, qi.wang@intel.com,
yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com,
Toshiharu Okada <toshiharu-linux@dsn.okisemi.com>
Subject: Re: spi_topcliff_pch: reload issue
Date: Wed, 2 Mar 2011 15:07:56 -0700 [thread overview]
Message-ID: <20110302220756.GC22854@angua.secretlab.ca> (raw)
In-Reply-To: <7FC6F7C4A6284C0FBD95D71D76B7528D@hacdom.okisemi.com>
On Tue, Feb 22, 2011 at 10:22:11AM +0900, Tomoya MORINAGA wrote:
> Hi,
>
> issue: after reload the spi module, it can't do SPI communication.
>
> We have faced issue when execute the following command.
> insmod xxx.ko(Then, /dev/spidev0.0 is created with success)
> rmmod xxx.ko (Then, /dev/spidev0.0 is deleted with success)
> insmod xxx.ko(Then, /dev/spidev0.0 is created, however, below error message is showed)
>
> 0000:02:0c.1: registered master spi0
> 0000:02:0c.1: chipselect 0 already in use
> 0000:02:0c.1: can't create new device for spidev
>
> Do you have any information about the above ?
Nope, I'm not an expert on that driver, but it definitely looks like a
bug! :-) It *looks* like the spi_device slaves are not getting unregistered
when the driver unloads. That's where I would start investigating.
The bug could either be in core code or the device driver itself, but
I don't know without digging deeper.
g.
next prev parent reply other threads:[~2011-03-02 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 1:22 spi_topcliff_pch: reload issue Tomoya MORINAGA
2011-03-02 22:07 ` Grant Likely [this message]
2011-02-22 12:00 Tomoya MORINAGA
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=20110302220756.GC22854@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=dbrownell@users.sourceforge.net \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morinaga526@dsn.okisemi.com \
--cc=qi.wang@intel.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=yong.y.wang@intel.com \
/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).