RE: Bringing up the BRCM43362 on Beaglebone Black

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The missed interrupts issue sounds likely.  There are pins on the module
that I do not have connected to the Beaglebone board.  I wanted to run
jumpers from the module to the P9 header on the Beaglebone.  I can define
gpios as input or output in the pinmux definition for mmc1, but I do not
know how to get the driver to recognize these and use them.  I tried
grepping the brcmfmac source code for a clue, but I did not find any
reference to any pin definitions.

How do I associate these gpio lines with the driver?
 



-----Original Message-----
From: linux-omap-owner@xxxxxxxxxxxxxxx
[mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren
Sent: Thursday, June 9, 2016 2:44 AM
To: Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx>
Cc: linux-omap@xxxxxxxxxxxxxxx
Subject: Re: Bringing up the BRCM43362 on Beaglebone Black

* Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx> [160608 13:46]:
> Some progress, but I'm hoping that someone can give me a clue...
> 
> I have set up the pins on mmc0 according to the TI pinmux tool and I 
> am following the example from the kernel documentation which shows how 
> to setup a node with properties controlling the Broadcom wireless 
> device.  (See the dtsi snippets below)
> 
> The board detects the 43362 module and attempts to load the firmware 
> and nvram data.  Unfortunately, inserting the module after the board 
> is up causes things to die and booting with the module in the SDIO 
> slot causes me to end up at the initramfs prompt.

Sounds like possibly 43362 driver bug maybe. Could be caused by spurious or
missed interrupts. You may need to add the sdio dat1 remuxing to GPIO during
idle using the pinctrl named states in your dts file.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the
body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at
http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux