From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<socketcan-core@lists.berlios.de>, <sameo@linux.intel.com>,
<21cnbao@gmail.com>, <chripell@fsfe.org>, <w.sang@pengutronix.de>,
<wg@grandegger.com>
Cc: "David Miller" <davem@davemloft.net>, <margie.foster@intel.com>,
<kok.howg.ewe@intel.com>, <joel.clark@intel.com>,
<andrew.chih.howe.khor@intel.com>, <yong.y.wang@intel.com>,
<qi.wang@intel.com>
Subject: can: About Socket CAN with MSI issue
Date: Wed, 27 Oct 2010 13:29:15 +0900 [thread overview]
Message-ID: <002801cb758f$876aaf00$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 20101026.105206.15244527.davem@davemloft.net
We have faced issue when our CAN diriver whose MSI is enabled, after installing the driver,
once remove the driver and install the driver again,
As a result, interupt handler of the driver is not called again.
Do you have any information or suggestion about the above issue?
As to the our latest CAN driver,
please refer to followoing patch posted by me.
[PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings
Thanks, Tomoya(OKI SEMICONDUCTOR CO., LTD.)
next prev parent reply other threads:[~2010-10-27 4:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 0:04 [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya
2010-10-26 17:52 ` David Miller
2010-10-26 17:55 ` David Miller
2010-10-26 18:27 ` Wolfgang Grandegger
2010-10-26 18:52 ` Marc Kleine-Budde
2010-10-27 11:27 ` [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix buildwarnings Tomoya MORINAGA
2010-10-27 11:57 ` Wolfgang Grandegger
2010-10-27 11:58 ` Marc Kleine-Budde
2010-10-27 13:14 ` Marc Kleine-Budde
2010-10-27 0:50 ` [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Fix build warnings Tomoya MORINAGA
2010-10-27 4:29 ` Tomoya MORINAGA [this message]
2010-10-27 7:31 ` can: About Socket CAN with MSI issue Wolfgang Grandegger
2010-10-27 7:56 ` Dave Airlie
2010-10-27 11:41 ` 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='002801cb758f$876aaf00$66f8800a@maildom.okisemi.com' \
--to=tomoya-linux@dsn.okisemi.com \
--cc=21cnbao@gmail.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=chripell@fsfe.org \
--cc=davem@davemloft.net \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=margie.foster@intel.com \
--cc=netdev@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=sameo@linux.intel.com \
--cc=socketcan-core@lists.berlios.de \
--cc=w.sang@pengutronix.de \
--cc=wg@grandegger.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 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.