[linux-sunxi] USB boot lost in 4.3+ ?

2016-01-19 Thread Igor Pecovnik
Hello,

In recent kernel(s) CONFIG_PHY_SUN4I_USB is only possible to build as module.
... so we can't boot from USB drive.

I try many combinations, but PHY stays as module.
https://github.com/igorpecovnik/lib/blob/master/config/linux-sunxi-dev.config

Any clues?

BR, Igor

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [linux-sunxi] Banana Pi mainline ALSA support

2016-01-19 Thread Dan MacDonald
I've noticed another odd thing with the current ALSA sun4i-codec under
4.4.0 on the BananaPi.

Despite the fact that alsamixer sees the BPi audio device, it is (mostly)
working and its also visible under /proc/asound/cards and
/proc/asound/devices, dmesg says there are no ALSA devices:

[3.987175] ALSA device list:
[3.990168]   No soundcards found.


On Tue, Jan 19, 2016 at 8:11 AM, Dan MacDonald  wrote:

> Hi Danny!
>
> Thanks for your reply!
>
> You inspired me to have another go with ALSA on my BPi and now I've got
> sound output working at full volume. To get output working at full volume,
> both 'Power Amplifier DAC' and 'Power Amplifier Mute' have to be unmuted
> and everything else must be muted. If I unmute anything else the sound cuts
> out.
>
> This has highlighted anoter problem I forgot to mention in my last post
> and that is I only have one alsamixer playback control with a volume slider
> (Power Amplifier) and this is the only one that doesn't have a mute control
> but as I said I can mute audio output by changing the combination of mute
> options from the one I mentioned before.
>
> $ amixer contents
> numid=2,iface=MIXER,name='Left Mixer Left DAC Playback Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=off
> numid=5,iface=MIXER,name='Power Amplifier DAC Playback Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=on
> numid=6,iface=MIXER,name='Power Amplifier Mixer Playback Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=off
> numid=7,iface=MIXER,name='Power Amplifier Mute Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=on
> numid=1,iface=MIXER,name='Power Amplifier Volume'
>   ; type=INTEGER,access=rw---R--,values=1,min=0,max=63,step=0
>   : values=62
>   | dBscale-min=-63.00dB,step=1.00dB,mute=1
> numid=4,iface=MIXER,name='Right Mixer Left DAC Playback Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=off
> numid=3,iface=MIXER,name='Right Mixer Right DAC Playback Switch'
>   ; type=BOOLEAN,access=rw--,values=1
>   : values=off
>
>
> Thanks!
>
>
> On Tue, Jan 19, 2016 at 1:54 AM, Danny Milosavljevic <
> dan...@scratchpost.org> wrote:
>
>> Hi Dan,
>>
>> On Mon, 18 Jan 2016 14:32:48 -0800 (PST)
>> Dan MacDonald  wrote:
>>
>> > I recently asked about the status of ALSA audio for the BPi in mainline
>> on
>> > the lemaker forums and I was pointed towards this patch:
>> >
>> >
>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit?id=38e633f3f3756b5630c5eb66042e776d86764296
>>
>> That's correct.
>>
>> > Not all of the ALSA mixer
>> > controls are present and the ones that are seem to be incorrectly
>> labelled
>> > so it clearly needs some work yet:
>>
>> Which one is incorrectly labeled?
>>
>> What does
>>
>> $ amixer contents
>>
>> say?
>>
>> Make sure that you unmute (using the "M" key in alsamixer) only one of
>> Power Amplifier DAC, Power Amplifier Mixer. If you unmute both, it will
>> sometimes cause destructive interference. I'd suggest to mute Power
>> Amplifier Mixer - fewers things that can go wrong.
>>
>> Things are unmuted in alsamixer when the box below the slider glows
>> green, muted when it's transparent and says "MM".
>>
>> Note that "Power Amplifier Mute" needs to be unmuted (i.e. green) for
>> your headphones to work normally.
>>
>> > Is anybody here working on the BPi ALSA driver?
>> > Is there a more complete patch I can test?
>>
>> I'm working on a patch for more complete mixing in general - further work
>> is currently blocked waiting for answers to some technical questions.
>>
>> However, I doubt my patches would fix your playback volume problem. I
>> never had that problem before. The stuff I added is exclusively for
>> capturing and loopback (so far).
>>
>> (If you want to try, search for sun4i-codec posts on this list, by me. It
>> won't help, though)
>>
>> Regards,
>>Danny
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [linux-sunxi] [PATCH v2 16/26] drm: Add Allwinner A10 Display Engine support

2016-01-19 Thread Maxime Ripard
Hi,

On Sat, Jan 16, 2016 at 05:11:44PM +0200, Priit Laes wrote:
> > +struct drm_fbdev_cma *sun4i_framebuffer_init(struct drm_device *drm)
> > +{
> > +   drm_mode_config_reset(drm);
> > +
> > +   drm->mode_config.max_width = 8192;
> > +   drm->mode_config.max_height = 8192;
> 
> Shouldn't these be 1920 x 1080 as per A10 User manual?

1080p is what the SoC can output. However, to create its output, it
uses a combination of planes of 8192x8192, that you'll obviously have
to crop. This is the size of the plane that we are exposing here, not
what we can output (which is listed in the various connectors).

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature


[linux-sunxi] Re: SDIO WIFI (brcm43430)

2016-01-19 Thread Vishnu Patekar
Hello Arend,

On Tue, Jan 19, 2016 at 5:20 PM, Arend van Spriel  wrote:
> On 19-1-2016 2:30, Vishnu Patekar wrote:
>> Hello Arend,
>>
>> I've A83T BPI-m3 board, which includes AP6212(brcm43430). I'm trying
>> to make it work for mainline linux and brcm driver.
>>
>> After enabling mmc1, It could read vendor: 0x02d0 device: 0xa9a6. from
>> /sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1
>>
>> BRCM driver loads the firmware files, however, it gives below errors
>> and wlan0 is not available:
>>
>> dmesg | grep brcm
>> [1.187459] brcmfmac: brcmf_of_probe: interrupt could not be mapped
>
> Not sure whether this might cause an issue. Could be a devicetree issue.

Yes, it was a device tree issue, it's now fixed.

still, it's not working,
[2.319200] brcmfmac: brcmf_sdio_firmware_callback failed:
dev=mmc1:0001:1, err=0
.
.
[4.405585] brcmfmac: brcmf_sdio_remove Disconnected

detailed log with brcmfmac.debug=30, :http://pastebin.com/PbJYxFhP

>
> Regards,
> Arend
>
>> [1.194419] brcmfmac: F1 signature read @0x1800=0x1530a9a6
>> [1.197807] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive
>> strength init done for chip 43430 rev 0 pmurev 24
>> [2.310138] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
>> clkctl 0x50
>> [3.319433] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
>> clkctl 0x50
>> [4.349022] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
>> clkctl 0x50
>>
>>
>> There are no brcm43430 firmware files at
>> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/brcm
>> So, used firmware:
>> https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm/brcmfmac43430-sdio.bin
>> and .txt.
>>
>> Could you please help me in this regard ?
>>
>>
>> Regards,
>> Vishnu
>>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[linux-sunxi] Re: SDIO WIFI (brcm43430)

2016-01-19 Thread Arend van Spriel
On 19-1-2016 2:30, Vishnu Patekar wrote:
> Hello Arend,
> 
> I've A83T BPI-m3 board, which includes AP6212(brcm43430). I'm trying
> to make it work for mainline linux and brcm driver.
> 
> After enabling mmc1, It could read vendor: 0x02d0 device: 0xa9a6. from
> /sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1
> 
> BRCM driver loads the firmware files, however, it gives below errors
> and wlan0 is not available:
> 
> dmesg | grep brcm
> [1.187459] brcmfmac: brcmf_of_probe: interrupt could not be mapped

Not sure whether this might cause an issue. Could be a devicetree issue.

Regards,
Arend

> [1.194419] brcmfmac: F1 signature read @0x1800=0x1530a9a6
> [1.197807] brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive
> strength init done for chip 43430 rev 0 pmurev 24
> [2.310138] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
> clkctl 0x50
> [3.319433] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
> clkctl 0x50
> [4.349022] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100):
> clkctl 0x50
> 
> 
> There are no brcm43430 firmware files at
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/brcm
> So, used firmware:
> https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm/brcmfmac43430-sdio.bin
> and .txt.
> 
> Could you please help me in this regard ?
> 
> 
> Regards,
> Vishnu
> 

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [linux-sunxi] Banana Pi mainline ALSA support

2016-01-19 Thread Dan MacDonald
Hi Danny!

Thanks for your reply!

You inspired me to have another go with ALSA on my BPi and now I've got
sound output working at full volume. To get output working at full volume,
both 'Power Amplifier DAC' and 'Power Amplifier Mute' have to be unmuted
and everything else must be muted. If I unmute anything else the sound cuts
out.

This has highlighted anoter problem I forgot to mention in my last post and
that is I only have one alsamixer playback control with a volume slider
(Power Amplifier) and this is the only one that doesn't have a mute control
but as I said I can mute audio output by changing the combination of mute
options from the one I mentioned before.

$ amixer contents
numid=2,iface=MIXER,name='Left Mixer Left DAC Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=5,iface=MIXER,name='Power Amplifier DAC Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on
numid=6,iface=MIXER,name='Power Amplifier Mixer Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=7,iface=MIXER,name='Power Amplifier Mute Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on
numid=1,iface=MIXER,name='Power Amplifier Volume'
  ; type=INTEGER,access=rw---R--,values=1,min=0,max=63,step=0
  : values=62
  | dBscale-min=-63.00dB,step=1.00dB,mute=1
numid=4,iface=MIXER,name='Right Mixer Left DAC Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=3,iface=MIXER,name='Right Mixer Right DAC Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off


Thanks!


On Tue, Jan 19, 2016 at 1:54 AM, Danny Milosavljevic  wrote:

> Hi Dan,
>
> On Mon, 18 Jan 2016 14:32:48 -0800 (PST)
> Dan MacDonald  wrote:
>
> > I recently asked about the status of ALSA audio for the BPi in mainline
> on
> > the lemaker forums and I was pointed towards this patch:
> >
> >
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit?id=38e633f3f3756b5630c5eb66042e776d86764296
>
> That's correct.
>
> > Not all of the ALSA mixer
> > controls are present and the ones that are seem to be incorrectly
> labelled
> > so it clearly needs some work yet:
>
> Which one is incorrectly labeled?
>
> What does
>
> $ amixer contents
>
> say?
>
> Make sure that you unmute (using the "M" key in alsamixer) only one of
> Power Amplifier DAC, Power Amplifier Mixer. If you unmute both, it will
> sometimes cause destructive interference. I'd suggest to mute Power
> Amplifier Mixer - fewers things that can go wrong.
>
> Things are unmuted in alsamixer when the box below the slider glows green,
> muted when it's transparent and says "MM".
>
> Note that "Power Amplifier Mute" needs to be unmuted (i.e. green) for your
> headphones to work normally.
>
> > Is anybody here working on the BPi ALSA driver?
> > Is there a more complete patch I can test?
>
> I'm working on a patch for more complete mixing in general - further work
> is currently blocked waiting for answers to some technical questions.
>
> However, I doubt my patches would fix your playback volume problem. I
> never had that problem before. The stuff I added is exclusively for
> capturing and loopback (so far).
>
> (If you want to try, search for sun4i-codec posts on this list, by me. It
> won't help, though)
>
> Regards,
>Danny
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.