All of lore.kernel.org
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: alsa-devel@alsa-project.org
Cc: Fabio Estevam <festevam@gmail.com>
Subject: Re: Fwd: Issue on Linux 4.12-rc7 on iMX6 based board
Date: Thu, 29 Jun 2017 16:36:01 +0200	[thread overview]
Message-ID: <506978bc-2077-13bc-987b-f99aa413ca5a@eurekelettronica.it> (raw)
In-Reply-To: <c19fa7f1-17f3-1bd0-81a2-a916fac8c1ab@eurekelettronica.it>

On 06/29/2017 04:24 PM, gianluca wrote:
> On 06/29/2017 03:49 PM, Fabio Estevam wrote:
>> On Thu, Jun 29, 2017 at 10:39 AM, gianluca
>> <gianlucarenzi@eurekelettronica.it> wrote:
>>
>>> In the device-tree the sound node is so configured:
>>>
>>>>         sound {
>>>>                 compatible = "fsl,imx-audio-sgtl5000";
>>>>                 model = "imx6-ek360-sgtl5000";
>>>>                 ssi-controller = <&ssi1>;
>>>>                 audio-codec = <&sgtl5000>;
>>>>                 audio-routing =
>>>>                         "MIC_IN", "Mic Jack",
>>>>                         "Mic Jack", "Mic Bias",
>>>>                         "Headphone Jack", "HP_OUT";
>>>>                 mux-int-port = <1>;
>>>>                 mux-ext-port = <4>;
>>
>> This should be mux-ext-port = <3>;
>>
>
> I've already modified now.
>
>>> I do not know about the mux-int-port or mux-ext-port. The only thing
>>> I know
>>> is the hardware guy told me he routed the ssi (CLK and DAT) to:
>>>
>>> AUD3_TXC_R (i2s_sclk)
>>> AUD3_TXD   (i2s_din)
>>> AUD3_TXFS  (i2s_lrclk)
>>> AUD3_RXD   (i2s_dout)
>>> SYS_MCLK   (GPIO_0_CLKO sys_mclk)
>>
>> since you are using AUD3 pins.
>>
>
> So, are they good?
>
> My only concern is the value after the MSYS_CLK (GPIO_0_CCM_CLK01). It
> is 0x030b0. Is this correct for output clock signal?
>
>>>
>>> So I configured the pinmux for audio in the following way:
>>>
>>>>                 pinctrl_audmux: audmuxgrp {
>>>>                         fsl,pins = <
>>>>                                 /* SGTL5000 sys_mclk */
>>>>                                 MX6QDL_PAD_GPIO_0__CCM_CLKO1
>>>> 0x030b0
>
> The remaining pins seems to be configured as a lot of boards in the
> current 4.12-rc7 kernel. So I can assume they are good.
>
>>>>                                 MX6QDL_PAD_CSI0_DAT4__AUD3_TXC
>>>> 0x130b0
>>>>                                 MX6QDL_PAD_CSI0_DAT5__AUD3_TXD
>>>> 0x110b0
>>>>                                 MX6QDL_PAD_CSI0_DAT6__AUD3_TXFS
>>>> 0x130b0
>>>>                                 MX6QDL_PAD_CSI0_DAT7__AUD3_RXD
>>>> 0x130b0
>>>>                         >;
>>>>                 };
>>>
>>>
>>
>> They should be good.
>>
>>> How can I check or dump the SGTL5000 registers?
>>
>> cat /sys/kernel/debug/regmap/xxx
>>
>
> I am missing the regmap. Should I configure kernel with additional
> CONFIG_ ?
>
> I started from the imxv6_imxv7_defconfig, then modified to have the
> correct drivers module as built-in or dynamic.
>
> Maybe am I missing something else??? :-(
>

The funny thing is I can clearly hear the 'POP' of the speaker after 
some seconds the end of the audio stream...

> # aplay /usr/share/sounds/alsa/Front_Right.wav




-- 
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

      parent reply	other threads:[~2017-06-29 14: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
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 [this message]

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=506978bc-2077-13bc-987b-f99aa413ca5a@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.