All of lore.kernel.org
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: Fabio Estevam <festevam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Fwd: Issue on Linux 4.12-rc7 on iMX6 based board
Date: Mon, 3 Jul 2017 11:36:28 +0200	[thread overview]
Message-ID: <5d5f3326-8412-1af2-ac6f-ba3c5adf0013@eurekelettronica.it> (raw)
In-Reply-To: <259c247e-3638-f814-932a-ec5a2c9200b5@eurekelettronica.it>

Now I did some great steps ahead! ;-)

I can assume there is some misconfigured alsa stuff in my debootstrapped 
armhf jessie distro!!!

First step: from Barebox bootloader I tried to move on/off all pins 
connected to the SGTL5000 from SoC iMX6. They are moving good, so I can 
assume _NO_HARDWARE_ issue.

Second step: burn a ubuntu armhf image (boundary-devices-jessie) to 
match up my system-boot (/etc/fstab and /etc/inittab), adding the 
/lib/modules/4.12-rc7/ directory and drivers, and add the uImage for 
4.12-rc7 on the sdcard.

Third step: burn on the sdcard the Barebox bootloader instead of the 
(unrunningble) u-boot for another board (Nitrogen).

Fourth step: turn on my board with this sdcard.

Sound is working. The levels of the capabilities (PCM, MIC, DAC, ...) 
are settable and they are working fine.

I can play and I can record. The only thing is the driver can use only 
S24_LE as frequeny for recording but afterall everything is working as 
expected.

Now the biggest question:

WTF are working alsa or its configuration in a deboostrapped armhf 
distribution? Actually this distro was upgraded two times:

1- Wheezy armel
2- Wheezy armel + armhf
3- Wheezy armhf
4- Jessie armhf
5- apt get dist-upgrade...

Something in between was wrong with alsa. Any help or configuration file 
to fix this issue???

> # aplay -L
> null
>     Discard all samples (playback) or generate zero samples (capture)
> default:CARD=imx6ek360sgtl50
>     imx6-ek360-sgtl5000,
>     Default Audio Device
> sysdefault:CARD=imx6ek360sgtl50
>     imx6-ek360-sgtl5000,
>     Default Audio Device
> dmix:CARD=imx6ek360sgtl50,DEV=0
>     imx6-ek360-sgtl5000,
>     Direct sample mixing device
> dsnoop:CARD=imx6ek360sgtl50,DEV=0
>     imx6-ek360-sgtl5000,
>     Direct sample snooping device
> hw:CARD=imx6ek360sgtl50,DEV=0
>     imx6-ek360-sgtl5000,
>     Direct hardware device without any conversions
> plughw:CARD=imx6ek360sgtl50,DEV=0
>     imx6-ek360-sgtl5000,
>     Hardware device with all software conversions

>
>
> # aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: imx6ek360sgtl50 [imx6-ek360-sgtl5000], device 0: HiFi sgtl5000-0 []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> root@nitrogen:~# arecord -l
> **** List of CAPTURE Hardware Devices ****
> card 0: imx6ek360sgtl50 [imx6-ek360-sgtl5000], device 0: HiFi sgtl5000-0 []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0


May I have a simple configuration file for this?


On 06/29/2017 06:28 PM, gianluca wrote:
> On 06/29/2017 04:30 PM, Fabio Estevam wrote:
>> On Thu, Jun 29, 2017 at 11:24 AM, gianluca
>> <gianlucarenzi@eurekelettronica.it> wrote:
>>
>>> So, are they good?
>>
>> If your hardware really uses these pins, then yes :-)
>>
>
> Now looking at other boards where our hardware-guy took the inspiration
> (i.e. iMX6 Rex from Fedevel) the device-tree is the same as mine.
>
>> MX6QDL_PAD_GPIO_0__CCM_CLKO1        0x030b0
>
> 0x130b0 or 0x030b0 the only difference is the PAD_CTL_HYS      (1 << 16)
>
> Maybe more strong to noise, but basically they are the same.
>
> But I found an issue when playing data from aplay without specifing the
> device or specifying one:
>
>> # aplay /usr/share/sounds/alsa/Front_Center.wav
>> Playing WAVE 'Front_Center.wav' : Signed 16 bit Little Endian, Rate
>> 48000 Hz, Mono
>
> or
>
>> # aplay -D hw:0,0 /usr/share/sounds/alsa/Front_Right.wav
>> Playing WAVE 'Front_Center.wav' : Signed 16 bit Little Endian, Rate
>> 48000 Hz, Mono
>> aplay: set_params:1233: Sample format non available
>> Available formats:
>> - S24_LE
>
> Maybe some ALSA misconfigured????
>
> This distro is a bootstrapped jessie Debian 8, so some configuration
> could be missing or not-so-good-configured.
>

Regards,
-- 
Eurek s.r.l.                          |
Electronic Engineering                | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212

  reply	other threads:[~2017-07-03  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 15:32 Issue on Linux 4.12-rc7 on iMX6 based board gianluca
2017-06-28 15:34 ` Fwd: " gianluca
2017-06-29 11:37   ` Fabio Estevam
2017-06-29 13:39     ` gianluca
2017-06-29 13:49       ` Fabio Estevam
2017-06-29 14:24         ` gianluca
2017-06-29 14:30           ` Fabio Estevam
2017-06-29 16:28             ` gianluca
2017-07-03  9:36               ` gianluca [this message]
2017-07-03 11:08                 ` Fwd: Issue on Linux 4.12-rc7 on iMX6 based board [SOLVED] gianluca
2017-06-29 16:59             ` Fwd: Issue on Linux 4.12-rc7 on iMX6 based board gianluca
2017-06-29 14:36           ` gianluca

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=5d5f3326-8412-1af2-ac6f-ba3c5adf0013@eurekelettronica.it \
    --to=gianlucarenzi@eurekelettronica.it \
    --cc=alsa-devel@alsa-project.org \
    --cc=festevam@gmail.com \
    /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.