All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mylene Josserand" <Mylene.Josserand@navocap.com>
To: linux-can@vger.kernel.org
Subject: [imx27 - mcp251x] MCP251x does not work in static ?
Date: Wed, 10 Apr 2013 15:07:56 +0200	[thread overview]
Message-ID: <CA78C307B8F06747967D122FC656B153774451@SERVEUR0.nvp.local> (raw)

Hi everyone,


I have posted in December 2012 a post about "[mcp251x - spi] Blocked to 
"wait_for_completion"".

To resolve the problem of CAN/spi and others, I am currently updating 
our kernel to the version 3.8.2 ! The SoC is a IMX27 and the CAN 
controller is MCP2515.

Currently, I have another problem with the MCP251x driver.

When I compile the driver in static, the kernel stopped booting. With 
some printk, the driver is blocked at the function "spi_write" of the 
function "mcp251x_hw_reset". The dmesg with my outputs :

"
spi_imx imx27-cspi.0: master is unqueued, this is deprecated
spi_imx imx27-cspi.0: probed
CAN device driver interface
mcp251x_can_init
mcp251x_clean
mcp251x_can_probe
mcp251x_hw_probe
mcp251x_hw_reset
mcp251x_hw_reset : spi_write : start
"

I thought that it was a spi problem because of the warning "master is 
unqueued, this is deprecated" but in fact the spi works.
One surprising thing (for me) is that the MCP251x compiled in module is 
probed ! (I did not test it yet)

"
root@navocap:~# modprobe mcp251x
mcp251x_can_init
sdrv->probe = bf09047c
sdrv->remove = bf08f348
mcp251x_clean
mcp251x_can_probe
mcp251x_hw_probe
mcp251x_hw_reset
mcp251x_hw_reset : spi_write : start
mcp251x_hw_reset : spi_write : end
mcp251x_read_reg
mcp251x_spi_trans
mcp251x_hw_reset : end
mcp251x_hw_probe : hw_reset done
mcp251x_read_reg
mcp251x_spi_trans
mcp251x_read_reg
mcp251x_spi_trans
mcp251x_hw_sleep
mcp251x_write_reg
mcp251x_spi_trans
mcp251x spi0.0: probed
"

I do not understand why is it probed in module and not in static.
Do you have a suggestion ?
I thought that maybe the spi has not finished to be configured but how 
know that ?
Do you think that it is a spi problem and not a MCP251x problem ?

Best regards,

-- 
Mylène JOSSERAND
Navocap

             reply	other threads:[~2013-04-10 13:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 13:07 Mylene Josserand [this message]
2013-04-10 13:39 ` [imx27 - mcp251x] MCP251x does not work in static ? Marc Kleine-Budde
2013-04-10 14:11   ` Mylene Josserand
2013-04-10 15:30     ` Marc Kleine-Budde
2013-04-11  7:39       ` Mylene Josserand
2013-04-11  7:49         ` Marc Kleine-Budde
2013-04-11  8:04           ` Mylene Josserand
2013-04-11  8:39             ` Marc Kleine-Budde
2013-04-11  9:22               ` Mylene Josserand
2013-04-11  9:49                 ` Marc Kleine-Budde
2013-04-11 14:39                   ` Mylene Josserand
2013-04-11 15:09                     ` Marc Kleine-Budde
2013-04-12  9:24                       ` Mylene Josserand
2013-04-12  9:49                         ` Marc Kleine-Budde
2013-04-12  9:36                     ` Marc Kleine-Budde
2013-04-12  9:40                       ` Mylene Josserand
2013-04-12  9:48                         ` Marc Kleine-Budde
2013-04-11  8:36           ` RFC: [PATCH] can: mcp251x: add missing IRQF_ONESHOT to request_threaded_irq Marc Kleine-Budde
2013-04-12 11:16             ` Marc Kleine-Budde

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=CA78C307B8F06747967D122FC656B153774451@SERVEUR0.nvp.local \
    --to=mylene.josserand@navocap.com \
    --cc=linux-can@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 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.