Enable dummy regulators in the kernel
28 Авг 2015 г. 14:30 пользователь "Iain Hunter" <drhunte...@gmail.com>
написал:
> Hi
>
> This is not good. You have tried to start mmc3 but it failed to get a
> regulator, so may not have continued its initialisation - i don't know how
> driver behaves in this case.
> omap_hsmmc 47810000.mmc: unable to get vmmc regulator -517
>
> So suggestion would be to trace omap_hsmmc driver to understand why it
> fails to get a regulator.
> Iain
>
> On 28 August 2015 at 04:34, Dileep <drdilee...@gmail.com> wrote:
>
>> Hi lain,
>>
>> I have configured MMC3 for SDIO communiction. but still sdio
>> communication is not up.
>>
>> If clock is not enabled by default for MMC3 how can it be done in device
>> tree,
>>
>> dmesg log shows:
>> [ 4.259093] omap_hsmmc 47810000.mmc: unable to get vmmc regulator -517
>>
>>
>> Device tree configurations.
>>
>> wl12xx_vmmc: fixedregulator@2 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&wl12xx_gpio>;
>> compatible = "regulator-fixed";
>> regulator-name = "vwl1271";
>> regulator-min-microvolt = <1800000>;
>> regulator-max-microvolt = <1800000>;
>> gpio = <&gpio0 27 0>;
>> startup-delay-us = <70000>;
>> enable-active-high;
>> };
>>
>> mmc3_pins: pinmux_mmc3_pins {
>> pinctrl-single,pins = <
>> 0x3C (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat3 */
>> 0x38 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat2 */
>> 0x34 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat1 */
>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_dat0 */
>> 0x8c (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_clk */
>> 0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* mmc2_cmd */
>> >;
>> };
>>
>> &mmc3 {
>> /* these are on the crossbar and are outlined in the
>> xbar-event-map element */
>> dmas = <&edma 32 &edma 33>;
>> dma-names = "tx", "rx";
>>
>> status = "okay";
>> vmmc-supply = <&wl12xx_vmmc>;
>> ti,non-removable;
>> bus-width = <4>;
>> cap-power-off-card;
>> pinctrl-names = "default";
>> pinctrl-0 = <&mmc3_pins>;
>>
>> #address-cells = <1>;
>> #size-cells = <0>;
>> wlcore: wlcore@2 {
>> compatible = "ti,wl1271";
>> reg = <2>;
>> interrupt-parent = <&gpio0>;
>> interrupts = <26 0x4>; /* gpio 31 */
>> ref-clock-frequency = <38400000>;
>> };
>> };
>>
>> &edma {
>> ti,edma-xbar-event-map = /bits/ 16 <1 32 2 33>;
>> };
>>
>> On Thu, Aug 27, 2015 at 10:03 PM, Iain Hunter <drhunte...@gmail.com>
>> wrote:
>>
>>> Did you use device tree in the end or modify a board.c?
>>> If so that looks like the mmc port is not being probed correctly as it
>>> is not defined. You should at least get some activity on mmc to try and
>>> read the type of "sd card" on this bus. This should identify as a wl12xx
>>> and then load the drivers when you insmod wlcore_sdio
>>> Iain
>>>
>>> On 26 August 2015 at 09:56, Dileep <drdilee...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> When i add wl12xx module, none of the functions from wl12xx and wlcore
>>>> are getting called.
>>>>
>>>> logs:
>>>> root@arm:~# modprobe wlcore_sdio
>>>> [ 48.682409]
>>>> [ 48.682409] ********** wl1271_init ************
>>>> [ 48.690385]
>>>> [ 48.690385] ********** sdio_register_driver ************
>>>> [ 48.708615]
>>>> [ 48.708615] ********** sdio_register_driver : wl1271_sdio
>>>> ************
>>>> root@arm:~# modprobe wl12xx
>>>> [ 57.901415]
>>>> [ 57.901415] ********** Country : COUNTRY=00 *********
>>>> [ 57.908006] cfg80211: Calling CRDA to update world regulatory domain
>>>> [ 58.061324]
>>>> [ 58.061324] ********** ieee80211_init ************
>>>> [ 58.067658]
>>>> [ 58.067658] ********** ieee80211_init 1 ************
>>>> [ 58.076820]
>>>> [ 58.076820] ********** ieee80211_init 2 ************
>>>> [ 58.086826]
>>>> [ 58.086826] ********** ieee80211_init 3 ************
>>>> root@arm:~# [ 58.207791] cfg80211: World regulatory domain updated:
>>>> [ 58.213206] cfg80211: DFS Master region: unset
>>>> [ 58.217588] cfg80211: (start_freq - end_freq @ bandwidth),
>>>> (max_antenna_gain, max_eirp), (dfs_cac_time)
>>>> [ 58.229554] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
>>>> (N/A, 2000 mBm), (N/A)
>>>> [ 58.237609] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz),
>>>> (N/A, 2000 mBm), (N/A)
>>>> [ 58.246721] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz),
>>>> (N/A, 2000 mBm), (N/A)
>>>> [ 58.255431] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz,
>>>> 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
>>>> [ 58.265659] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz,
>>>> 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
>>>> [ 58.275796] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz),
>>>> (N/A, 2000 mBm), (0 s)
>>>> [ 58.284697] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz),
>>>> (N/A, 2000 mBm), (N/A)
>>>> [ 58.293341] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz),
>>>> (N/A, 0 mBm), (N/A)
>>>>
>>>> root@arm:~# lsmod
>>>> Module Size Used by
>>>> wl12xx 64379 0
>>>> wlcore 213095 1 wl12xx
>>>> mac80211 631232 2 wl12xx,wlcore
>>>> cfg80211 518978 2 mac80211,wlcore
>>>> rfkill 20618 1 cfg80211
>>>> wlcore_sdio 8050 0
>>>> snd_soc_evm 7798 0
>>>> omap_rng 5144 0
>>>> rng_core 8712 1 omap_rng
>>>> tilcdc 31000 0
>>>> snd_soc_tlv320aic32x4 16689 1
>>>> snd_soc_davinci_mcasp 18424 2
>>>> snd_soc_edma 1166 1 snd_soc_davinci_mcasp
>>>> uio_pdrv_genirq 3625 0
>>>> uio 9898 1 uio_pdrv_genirq
>>>> root@arm:~#
>>>>
>>>>
>>>> On Thu, Aug 20, 2015 at 4:18 PM, Iain Hunter <drhunte...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> As a follow up I agree with the previous statement that wl127x drivers
>>>>> have no device tree support. So you'll need to merge device tree support
>>>>> from wl18xx drivers. As far as I can remember there are no major changes
>>>>> to
>>>>> parameters passed by device tree to WiFi driver from wl127x to wl18xx. As
>>>>> long as you successfully pass the wl12xx probe function without an error
>>>>> you should be ok. Caveat is that I've not done this exercise.
>>>>> Iain
>>>>> On 19 Aug 2015 15:56, <drhunte...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>> Which wilink device are you building for?
>>>>>> The wl18xx family is now fully supported in 4.1 kernel. There is a
>>>>>> device tree file for the wl1835 cape in the kernel that is best place to
>>>>>> look.
>>>>>> If you are looking at wl127x or wl128x then device tree will be
>>>>>> similar but you'll need to build the Wi-Fi drivers out of tree.
>>>>>> For the wl1835 cape look at the ti processor wiki for a page to
>>>>>> describe full build and configuration on 4.1 kernel.
>>>>>> Iain
>>>>>>
>>>>>> --
>>>>>> For more options, visit http://beagleboard.org/discuss
>>>>>> ---
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "BeagleBoard" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> beagleboard+unsubscr...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>> For more options, visit http://beagleboard.org/discuss
>>>>> ---
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "BeagleBoard" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> beagleboard+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> For more options, visit http://beagleboard.org/discuss
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "BeagleBoard" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> beagleboard+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/_Edxe-s1MxQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
