From: alexanders83@web.de (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3 v8] mailbox: Enable BCM2835 mailbox support
Date: Fri, 08 May 2015 10:33:53 +0200 [thread overview]
Message-ID: <2464203.68HkYCAlx7@kongar> (raw)
In-Reply-To: <87mw1grwnn.fsf@eliezer.anholt.net>
On Thursday 07 May 2015, 12:54:20 wrote Eric Anholt:
> Noralf Tr?nnes <noralf@tronnes.org> writes:
>
> > Den 05.05.2015 22:27, skrev Eric Anholt:
> >> From: Lubomir Rintel <lkundrak@v3.sk>
> >>
> >> This mailbox driver provides a single mailbox channel to write 32-bit
> >> values to the VPU and get a 32-bit response. The Raspberry Pi
> >> firmware uses this mailbox channel to implement firmware calls, while
> >> Roku 2 (despite being derived from the same firmware tree) doesn't.
> >>
> >> The driver was originally submitted by Lubomir, based on the
> >> out-of-tree 2708 mailbox driver. Eric Anholt fixed it up for
> >> upstreaming, with the major functional change being that it now has no
> >> notion of multiple channels (since that is a firmware-dependent
> >> concept) and instead the raspberrypi-firmware driver will do that
> >> bit-twiddling in its own messages.
> > ...
> >> +static struct platform_driver bcm2835_mbox_driver = {
> >> + .driver = {
> >> + .name = "bcm2835-mbox",
> >> + .owner = THIS_MODULE,
> >> + .of_match_table = bcm2835_mbox_of_match,
> >> + },
> >> + .probe = bcm2835_mbox_probe,
> >> + .remove = bcm2835_mbox_remove,
> >> +};
> >> +module_platform_driver(bcm2835_mbox_driver);
> >
> > I have tested this driver and the firmware driver booting directly
> > from the VideoCore bootloader (no uboot).
> > The mailbox driver loads too late to turn on USB power:
>
> Yeah, I have a patch on my branches that returns -EPROBE_DEFER when
> trying to get a power domain and not finding the provider. It was
> rejected by the maintainers in favor of a proposed solution whose
> description I didn't quite follow.
Do you have a link for this thread?
> > This silences the warning:
> > struct raspberrypi_power_domain raspberrypi_power_domain_usb = {
> > .base = {
> > .power_on_latency_ns = 600000000,
>
> Oh, nice. Thanks!
Well, Using a timeout for dependencies seems odd to me.
Regards,
Alexander
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexanders83@web.de>
To: linux-rpi-kernel@lists.infradead.org
Cc: "Eric Anholt" <eric@anholt.net>,
"Noralf Trønnes" <noralf@tronnes.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Jassi Brar" <jassisinghbrar@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH 2/3 v8] mailbox: Enable BCM2835 mailbox support
Date: Fri, 08 May 2015 10:33:53 +0200 [thread overview]
Message-ID: <2464203.68HkYCAlx7@kongar> (raw)
In-Reply-To: <87mw1grwnn.fsf@eliezer.anholt.net>
On Thursday 07 May 2015, 12:54:20 wrote Eric Anholt:
> Noralf Trønnes <noralf@tronnes.org> writes:
>
> > Den 05.05.2015 22:27, skrev Eric Anholt:
> >> From: Lubomir Rintel <lkundrak@v3.sk>
> >>
> >> This mailbox driver provides a single mailbox channel to write 32-bit
> >> values to the VPU and get a 32-bit response. The Raspberry Pi
> >> firmware uses this mailbox channel to implement firmware calls, while
> >> Roku 2 (despite being derived from the same firmware tree) doesn't.
> >>
> >> The driver was originally submitted by Lubomir, based on the
> >> out-of-tree 2708 mailbox driver. Eric Anholt fixed it up for
> >> upstreaming, with the major functional change being that it now has no
> >> notion of multiple channels (since that is a firmware-dependent
> >> concept) and instead the raspberrypi-firmware driver will do that
> >> bit-twiddling in its own messages.
> > ...
> >> +static struct platform_driver bcm2835_mbox_driver = {
> >> + .driver = {
> >> + .name = "bcm2835-mbox",
> >> + .owner = THIS_MODULE,
> >> + .of_match_table = bcm2835_mbox_of_match,
> >> + },
> >> + .probe = bcm2835_mbox_probe,
> >> + .remove = bcm2835_mbox_remove,
> >> +};
> >> +module_platform_driver(bcm2835_mbox_driver);
> >
> > I have tested this driver and the firmware driver booting directly
> > from the VideoCore bootloader (no uboot).
> > The mailbox driver loads too late to turn on USB power:
>
> Yeah, I have a patch on my branches that returns -EPROBE_DEFER when
> trying to get a power domain and not finding the provider. It was
> rejected by the maintainers in favor of a proposed solution whose
> description I didn't quite follow.
Do you have a link for this thread?
> > This silences the warning:
> > struct raspberrypi_power_domain raspberrypi_power_domain_usb = {
> > .base = {
> > .power_on_latency_ns = 600000000,
>
> Oh, nice. Thanks!
Well, Using a timeout for dependencies seems odd to me.
Regards,
Alexander
next prev parent reply other threads:[~2015-05-08 8:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 20:27 [PATCH 1/3 v6] dt/bindings: Add binding for the BCM2835 mailbox driver Eric Anholt
2015-05-05 20:27 ` Eric Anholt
2015-05-05 20:27 ` Eric Anholt
2015-05-05 20:27 ` [PATCH 2/3 v8] mailbox: Enable BCM2835 mailbox support Eric Anholt
2015-05-05 20:27 ` Eric Anholt
2015-05-07 17:28 ` Noralf Trønnes
2015-05-07 17:28 ` Noralf Trønnes
2015-05-07 17:28 ` Noralf Trønnes
2015-05-07 19:54 ` Eric Anholt
2015-05-07 19:54 ` Eric Anholt
2015-05-08 8:33 ` Alexander Stein [this message]
2015-05-08 8:33 ` Alexander Stein
2015-05-08 19:19 ` Eric Anholt
2015-05-08 19:19 ` Eric Anholt
2015-05-12 2:41 ` Stephen Warren
2015-05-12 2:41 ` Stephen Warren
2015-05-08 20:38 ` Noralf Trønnes
2015-05-08 20:38 ` Noralf Trønnes
2015-05-08 20:38 ` Noralf Trønnes
2015-05-12 15:28 ` Noralf Trønnes
2015-05-12 15:28 ` Noralf Trønnes
2015-05-05 20:27 ` [PATCH 3/3 v2] ARM: bcm2835: Add the mailbox to the device tree Eric Anholt
2015-05-05 20:27 ` Eric Anholt
2015-05-13 7:57 ` Lee Jones
2015-05-13 7:57 ` Lee Jones
2015-05-12 4:03 ` [PATCH 1/3 v6] dt/bindings: Add binding for the BCM2835 mailbox driver Jassi Brar
2015-05-12 4:03 ` Jassi Brar
2015-05-13 7:57 ` Lee Jones
2015-05-13 7:57 ` Lee Jones
2015-05-13 7:57 ` Lee Jones
2015-05-13 15:47 ` Jassi Brar
2015-05-13 15:47 ` Jassi Brar
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=2464203.68HkYCAlx7@kongar \
--to=alexanders83@web.de \
--cc=linux-arm-kernel@lists.infradead.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.