[opensuse-arm] /dev/vcio for accessing the raspi "mailbox" ?
On my raspi 3b+, I'm trying out some code for controlling WS2812 LEDs - https://github.com/jgarff/rpi_ws281x The code uses /dev/vcio for mailbox communications - I guess there is a module that provides this interface, but I can't find it. It looks like bcm2835_mailbox is the right one, and it is part of the kernel. I also see in dmesg: [ 9.267410] bcm2835-mbox 3f00b880.mailbox: mailbox enabled What am I missing? -- Per Jessen, Zürich (6.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi,
-----Original Message----- From: Per Jessen
Sent: 08 March 2019 14:57 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] /dev/vcio for accessing the raspi "mailbox" ? On my raspi 3b+, I'm trying out some code for controlling WS2812 LEDs -
https://github.com/jgarff/rpi_ws281x
The code uses /dev/vcio for mailbox communications - I guess there is a module that provides this interface, but I can't find it. It looks like bcm2835_mailbox is the right one, and it is part of the kernel. I also see in dmesg:
[ 9.267410] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
What am I missing?
I think /dev/vcio is a downstream feature only. So, not available on openSUSE kernel which uses upstream kernels. Guillaume IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. N�����r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�����Ǩ�
Guillaume Gardet wrote:
Hi,
-----Original Message----- From: Per Jessen
Sent: 08 March 2019 14:57 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] /dev/vcio for accessing the raspi "mailbox" ? On my raspi 3b+, I'm trying out some code for controlling WS2812 LEDs -
https://github.com/jgarff/rpi_ws281x
The code uses /dev/vcio for mailbox communications - I guess there is a module that provides this interface, but I can't find it. It looks like bcm2835_mailbox is the right one, and it is part of the kernel. I also see in dmesg:
[ 9.267410] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
What am I missing?
I think /dev/vcio is a downstream feature only. So, not available on openSUSE kernel which uses upstream kernels.
Thanks Guillaume so, what do I need to do to talk to the raspi mailbox? I tried creating /dev/vcio myself (majornum 100), but I'm clearly missing whatever it is that provides that interface. -- Per Jessen, Zürich (7.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 08 Mar 2019 17:11:21 +0100
Per Jessen
Guillaume Gardet wrote:
I think /dev/vcio is a downstream feature only. So, not available on openSUSE kernel which uses upstream kernels.
Thanks Guillaume
so, what do I need to do to talk to the raspi mailbox? I tried creating /dev/vcio myself (majornum 100), but I'm clearly missing
That's definitely the wrong way. This can only work around a broken driver that somehow does not trigger udev.
whatever it is that provides that interface.
A similar patch set has been submitted for sunXi this week. Look for code that looks like https://patchwork.kernel.org/patch/10836377/ for the broadcom. Torsten
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 8 Mar 2019 18:05:44 +0100
Torsten Duwe
On Fri, 08 Mar 2019 17:11:21 +0100 Per Jessen
wrote:
whatever it is that provides that interface.
A similar patch set has been submitted for sunXi this week. Look for code that looks like
https://patchwork.kernel.org/patch/10836377/
for the broadcom.
4.20 has drivers/mailbox/bcm2835-mailbox.c. It looks for "brcm,bcm2835-mbox" in the DT. Do you have that? Torsten -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Torsten Duwe wrote:
On Fri, 08 Mar 2019 17:11:21 +0100 Per Jessen
wrote: Guillaume Gardet wrote:
I think /dev/vcio is a downstream feature only. So, not available on openSUSE kernel which uses upstream kernels.
Thanks Guillaume
so, what do I need to do to talk to the raspi mailbox? I tried creating /dev/vcio myself (majornum 100), but I'm clearly missing
That's definitely the wrong way. This can only work around a broken driver that somehow does not trigger udev.
I was wondering. Looking at the bcm2835-mailbox driver, I see no char device being registered - there is another vcio driver out there, but tere is clearly some overlap with bcm2835-mailbox.
whatever it is that provides that interface.
A similar patch set has been submitted for sunXi this week. Look for code that looks like
https://patchwork.kernel.org/patch/10836377/
for the broadcom.
Thanks Torsten, I'll have a look. -- Per Jessen, Zürich (6.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 08 Mar 2019 18:19:13 +0100
Per Jessen
https://patchwork.kernel.org/patch/10836377/
for the broadcom.
Thanks Torsten, I'll have a look.
Ok, you have the driver and the DT node, as proven by the kernel message in your first mail, so forget my previous remarks. drivers/mailbox/mailbox.c creates an internal device, but I see no consumers besides rpi-firmware. As Guillaume has already noted, downstream had created a device node here, which is lacking upstream. Do you have a platform device named "raspberrypi-hwmon"? Torsten -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Torsten Duwe wrote:
On Fri, 08 Mar 2019 18:19:13 +0100 Per Jessen
wrote: https://patchwork.kernel.org/patch/10836377/
for the broadcom. Thanks Torsten, I'll have a look.
Ok, you have the driver and the DT node, as proven by the kernel message in your first mail, so forget my previous remarks.
drivers/mailbox/mailbox.c creates an internal device, but I see no consumers besides rpi-firmware. As Guillaume has already noted, downstream had created a device node here, which is lacking upstream.
It sounds like that's what I need to look at first.
Do you have a platform device named "raspberrypi-hwmon"?
Yup, got it: /sys/devices/platform/soc/soc:firmware/raspberrypi-hwmon /sys/bus/platform/devices/raspberrypi-hwmon /sys/bus/platform/drivers/raspberrypi-hwmon /sys/bus/platform/drivers/raspberrypi-hwmon/raspberrypi-hwmon /Per -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Guillaume Gardet
-
Per Jessen
-
Torsten Duwe