From: gianluca <gianlucarenzi@eurek.it>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Patrick Menschel <menschel.p@posteo.de>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: Testing CAN on Allwinner A20 / Banana Pi
Date: Mon, 21 Mar 2016 10:27:19 +0100 [thread overview]
Message-ID: <56EFBE77.2020408@eurek.it> (raw)
In-Reply-To: <56ED4725.8080209@pengutronix.de>
On 03/19/2016 01:33 PM, Marc Kleine-Budde wrote:
>>
>> Compiling to dtb and back to dts now resolves to
>>
>> can@01c2bc00 {
>> compatible = "allwinner,sun4i-a10-can";
>> reg = <0x1c2bc00 0x400>;
>> interrupts = <0x0 0x1a 0x4>;
>> clocks = <0x31 0x4>;
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <0x32>;
>> };
>>
>> That does look plausible from my perspective.
>>
>> Unfortunately I'm still missing /dev/can0 and have no clue why.
>
> CAN devices are network devices and will not show up in "/dev". Have a
> look at:
>
> ifconfig -a
>
>> If your Bpi works with legacy u-boot, I would try that next.
It is not enough having the can-core controller in dtsi only. The kernel
has to be compiled with a network/can/socketcan enabled and the specific
SoC can controller enabled in the same subarch structure.
i.e.: you will need to have:
in sunxi_defconfig:
CONFIG_CAN=y
CONFIG_CAN_SUN4I=y
Just my $0.2...
Hope this helps!
--
Eurek s.r.l. |
Electronic Engineering | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212
next prev parent reply other threads:[~2016-03-21 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 8:51 Testing CAN on Allwinner A20 / Banana Pi Patrick Menschel
2015-09-12 9:13 ` Marc Kleine-Budde
2015-09-12 13:40 ` Patrick Menschel
2016-03-19 12:27 ` Patrick Menschel
2016-03-19 12:33 ` Marc Kleine-Budde
2016-03-19 12:50 ` Patrick Menschel
2016-03-19 12:53 ` Marc Kleine-Budde
2016-03-21 9:27 ` gianluca [this message]
2016-03-21 13:05 ` Patrick Menschel
2016-03-21 16:14 ` Marc Kleine-Budde
2016-03-21 17:08 ` Patrick Menschel
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=56EFBE77.2020408@eurek.it \
--to=gianlucarenzi@eurek.it \
--cc=linux-can@vger.kernel.org \
--cc=menschel.p@posteo.de \
--cc=mkl@pengutronix.de \
/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.