simple-audio-card

simple-audio-card

[Jiří Prchal]

Hi everybody,
would be someone so kind and help me with my sound card?
My connection is:
cpu AT91SAM9G25 I2S (SSC0) --> codec TLV320AIC3106 <-- clock 12MHz
Codec is clock master.

dts related parts:

	sound {
		compatible = "simple-audio-card";
		simple-audio-card,name = "TLV320AIC3106";
		simple-audio-card,widgets =
			"Headphone", "Front Out",
			"Line", "Rear Out",
			"Line", "GSM Out",
			"Speaker", "Speaker",
			"Microphone", "Front In",
			"Line", "Rear In",
			"Line", "GSM In";
		simple-audio-card,routing =
			"Front Out", "HPLOUT",
			"Rear Out", "HPROUT",
			"GSM Out", "LLOUT",
			"SP_AMP INL", "MONO_LOUT",
			"Speaker", "SP_AMP OUTL",
			"MIC3L", "Front In",
			"LINE1R", "Rear In",
			"LINE1L", "GSM In";
		simple-audio-card,format = "i2s";
		simple-audio-card,bitclock-master = <&sound_master>;
		simple-audio-card,frame-master = <&sound_master>;
		simple-audio-card,aux-devs = <&speaker_amp>;

		simple-audio-card,cpu {
			sound-dai = <&ssc0>;
		};

		sound_master: simple-audio-card,codec {
			sound-dai = <&tlv320aic3106>;
			system-clock-frequency = <12000000>;
		};
	};

&ssc0 {
	#sound-dai-cells = <0>;
	status = "okay";
	pinctrl-0 = <&pinctrl_ssc0_tx_rx>;
};

&spi0 {
	status = "okay";
	cs-gpios =
		<&pioA 22 0
		 &pioC 14 0
		 &pioC 29 0
		 &pioA  4 0>;

	tlv320aic3106: codec@3 {
		compatible = "ti,tlv320aic3106";
		reg = <3>;
		spi-max-frequency = <1000000>;
		#sound-dai-cells = <0>;
		adc-settle-ms = <40>;
		ai3x-micbias-vg = <2>; /* 2.5V */
		status = "okay";
		DRVDD-supply = <&vcc_3v3>;
		AVDD-supply = <&vcc_3v3>;
		IOVDD-supply = <&vcc_3v3>;
		DVDD-supply = <&vcc_1v8>;
		ai3x-ocmv = <2>; /* 1.65V */
	};
};


In kernel 5.12 it worked fine, but I can't make it in either 5.15 or 5.17.

dmesg doesn't help at all, even with debug compilation switch:
...
[    1.203333] ssc f0010000.ssc: Atmel SSC device at 0x(ptrval) (irq 22)
...
[    1.616666] atmel_spi f0000000.spi: Using dma0chan2 (tx) and 
dma0chan3 (rx) for DMA transfers
...
[    1.639999] codec@3 enforce active low on chipselect handle
[    1.656666] at25 spi0.0: 128 KByte fm25 fram, pagesize 4096
[    1.696666] atmel_spi f0000000.spi: Atmel SPI Controller version 
0x212 at 0xf0000000 (irq 28)
...
[    3.033333] ALSA device list:
[    3.036666]   No soundcards found.

The only difference in 5.12 is:
[    3.869999] ALSA device list:
[    3.876666]   #0: TLV320AIC3106

So, what's wrong?
Thanks Jiri

Re: simple-audio-card

[Jiří Prchal]

Hi,
something strange with it. When I compile kernel without loadable module 
support (# CONFIG_MODULES is not set) it works.

On 10. 03. 22 17:33, Jiří Prchal wrote:
> Hi everybody,
> would be someone so kind and help me with my sound card?
> My connection is:
> cpu AT91SAM9G25 I2S (SSC0) --> codec TLV320AIC3106 <-- clock 12MHz
> Codec is clock master.
> 
> dts related parts:
> 
>      sound {
>          compatible = "simple-audio-card";
>          simple-audio-card,name = "TLV320AIC3106";
>          simple-audio-card,widgets =
>              "Headphone", "Front Out",
>              "Line", "Rear Out",
>              "Line", "GSM Out",
>              "Speaker", "Speaker",
>              "Microphone", "Front In",
>              "Line", "Rear In",
>              "Line", "GSM In";
>          simple-audio-card,routing =
>              "Front Out", "HPLOUT",
>              "Rear Out", "HPROUT",
>              "GSM Out", "LLOUT",
>              "SP_AMP INL", "MONO_LOUT",
>              "Speaker", "SP_AMP OUTL",
>              "MIC3L", "Front In",
>              "LINE1R", "Rear In",
>              "LINE1L", "GSM In";
>          simple-audio-card,format = "i2s";
>          simple-audio-card,bitclock-master = <&sound_master>;
>          simple-audio-card,frame-master = <&sound_master>;
>          simple-audio-card,aux-devs = <&speaker_amp>;
> 
>          simple-audio-card,cpu {
>              sound-dai = <&ssc0>;
>          };
> 
>          sound_master: simple-audio-card,codec {
>              sound-dai = <&tlv320aic3106>;
>              system-clock-frequency = <12000000>;
>          };
>      };
> 
> &ssc0 {
>      #sound-dai-cells = <0>;
>      status = "okay";
>      pinctrl-0 = <&pinctrl_ssc0_tx_rx>;
> };
> 
> &spi0 {
>      status = "okay";
>      cs-gpios =
>          <&pioA 22 0
>           &pioC 14 0
>           &pioC 29 0
>           &pioA  4 0>;
> 
>      tlv320aic3106: codec@3 {
>          compatible = "ti,tlv320aic3106";
>          reg = <3>;
>          spi-max-frequency = <1000000>;
>          #sound-dai-cells = <0>;
>          adc-settle-ms = <40>;
>          ai3x-micbias-vg = <2>; /* 2.5V */
>          status = "okay";
>          DRVDD-supply = <&vcc_3v3>;
>          AVDD-supply = <&vcc_3v3>;
>          IOVDD-supply = <&vcc_3v3>;
>          DVDD-supply = <&vcc_1v8>;
>          ai3x-ocmv = <2>; /* 1.65V */
>      };
> };
> 
> 
> In kernel 5.12 it worked fine, but I can't make it in either 5.15 or 5.17.
> 
> dmesg doesn't help at all, even with debug compilation switch:
> ...
> [    1.203333] ssc f0010000.ssc: Atmel SSC device at 0x(ptrval) (irq 22)
> ...
> [    1.616666] atmel_spi f0000000.spi: Using dma0chan2 (tx) and 
> dma0chan3 (rx) for DMA transfers
> ...
> [    1.639999] codec@3 enforce active low on chipselect handle
> [    1.656666] at25 spi0.0: 128 KByte fm25 fram, pagesize 4096
> [    1.696666] atmel_spi f0000000.spi: Atmel SPI Controller version 
> 0x212 at 0xf0000000 (irq 28)
> ...
> [    3.033333] ALSA device list:
> [    3.036666]   No soundcards found.
> 
> The only difference in 5.12 is:
> [    3.869999] ALSA device list:
> [    3.876666]   #0: TLV320AIC3106
> 
> So, what's wrong?
> Thanks Jiri

atmel usart and dma tx

[Jiří Prchal]

Hi everybody,
with kernel 5.17, at91sam9g25 running at 400MHz I discovered drop outs 
while I write data (64 to 128B) to ttyS by one call of write(). At speed 
230400 or 115200 Baud. It is not transmitted at once, there are random 
spaces long 200us to 1ms. It should use DMA so I think it could be 
transmitted at once.
Is there everything OK with DMA or some special setting needed?

dmesg:
[    1.636666] bus: 'platform': __driver_probe_device: matched device 
f801c000.serial with driver at91_usart_mode
[    1.636666] bus: 'platform': really_probe: probing driver 
at91_usart_mode with device f801c000.serial
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0-0: 2 0:0
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function 
usart0 group usart0-0 num 3
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0_rts-0: 1 0:2
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function 
usart0 group usart0_rts-0 num 2
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group 
selector 4 for usart0-0
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group 
selector 5 for usart0_rts-0
[    1.636666] at91_usart_mode f801c000.serial: no init pinctrl state
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function 
usart0 group usart0-0
[    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function 
usart0 group usart0_rts-0
[    1.639999] at91_usart_mode f801c000.serial: no sleep pinctrl state
[    1.643333] at91_usart_mode f801c000.serial: no idle pinctrl state
[    1.643333] Registering platform device 'atmel_usart_serial.1.auto'. 
Parent at f801c000.serial
[    1.643333] device: 'atmel_usart_serial.1.auto': device_add
[    1.643333] bus: 'platform': add device atmel_usart_serial.1.auto
[    1.643333] bus: 'platform': __driver_probe_device: matched device 
atmel_usart_serial.1.auto with driver atmel_usart_serial
[    1.643333] bus: 'platform': really_probe: probing driver 
atmel_usart_serial with device atmel_usart_serial.1.auto
[    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no of_node; 
not parsing pinctrl DT
[    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no default 
pinctrl state
[    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: GPIO lookup 
for consumer rs485-term
[    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: using 
device tree for GPIO lookup
[    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: using 
lookup tables for GPIO lookup
[    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: No GPIO 
consumer rs485-term found
[    1.649999] atmel_usart_serial.1.auto: ttyS2 at MMIO 0xf801c000 (irq 
= 24, base_baud = 8333333) is a ATMEL_SERIAL
[    1.656666] driver: 'atmel_usart_serial': driver_bound: bound to 
device 'atmel_usart_serial.1.auto'
[    1.656666] bus: 'platform': really_probe: bound device 
atmel_usart_serial.1.auto to driver atmel_usart_serial
[    1.656666] driver: 'at91_usart_mode': driver_bound: bound to device 
'f801c000.serial'
[    1.656666] bus: 'platform': really_probe: bound device 
f801c000.serial to driver at91_usart_mode

[   41.606666] atmel_usart_serial atmel_usart_serial.1.auto: using 
dma0chan6 for rx DMA transfers
[   41.613333] atmel_usart_serial atmel_usart_serial.1.auto: using 
dma0chan7 for tx DMA transfers

With kernel 4.5 spaces are there too, but shorter and less frequent.
Thanks for any help,
Jiri

[bug] atmel_serial RS485 TX to RX switching

[Jiří Prchal]

Hi everybody,
I found maybe a "bug":
kernel 5.17 on at91sam9g25 running at 400MHz usart configured in devtree to "linux,rs485-enabled-at-boot-time" is RX disabled during TX. This would be OK, but when TX is done, enabling RX takes too long (sometimes up to 500us or even more), this results in not capturing data answered from remote. RTS signal switching direction works as expected just after last stop bit.

[bug] atmel_serial RS485 TX to RX switching

[Jiří Prchal]

ping...

Hi everybody,
I found maybe a "bug":
kernel 5.17 on at91sam9g25 running at 400MHz usart configured in devtree to "linux,rs485-enabled-at-boot-time" is RX disabled during TX. This would be OK, but when TX is done, enabling RX takes too long (sometimes up to 500us or even more), this results in not capturing data answered from remote. RTS signal switching direction works as expected just after last stop bit.

Re: atmel usart and dma tx

[Tudor.Ambarus]

Hi, Jiří,

On 4/28/22 12:08, Jiří Prchal wrote:
> [Some people who received this message don't often get email from jiri.prchal@aksignal.cz. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
> 
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Hi everybody,
> with kernel 5.17, at91sam9g25 running at 400MHz I discovered drop outs
> while I write data (64 to 128B) to ttyS by one call of write(). At speed
> 230400 or 115200 Baud. It is not transmitted at once, there are random
> spaces long 200us to 1ms. It should use DMA so I think it could be
> transmitted at once.
> Is there everything OK with DMA or some special setting needed?

There are some concurrency problems with at-hdmac that happen at high
loads (check [1]), but I don't think it's related to your problem.
Can you do a flame graph to verify where in the code is the stall? Why
do you assume it's at the DMA level? Have you tried using usart without
DMA and verify if the stalling is still there?

> 
> dmesg:
> [    1.636666] bus: 'platform': __driver_probe_device: matched device
> f801c000.serial with driver at91_usart_mode
> [    1.636666] bus: 'platform': really_probe: probing driver
> at91_usart_mode with device f801c000.serial
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0-0: 2 0:0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function
> usart0 group usart0-0 num 3
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0_rts-0: 1 0:2
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function
> usart0 group usart0_rts-0 num 2
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group
> selector 4 for usart0-0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group
> selector 5 for usart0_rts-0
> [    1.636666] at91_usart_mode f801c000.serial: no init pinctrl state
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function
> usart0 group usart0-0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function
> usart0 group usart0_rts-0
> [    1.639999] at91_usart_mode f801c000.serial: no sleep pinctrl state
> [    1.643333] at91_usart_mode f801c000.serial: no idle pinctrl state
> [    1.643333] Registering platform device 'atmel_usart_serial.1.auto'.
> Parent at f801c000.serial
> [    1.643333] device: 'atmel_usart_serial.1.auto': device_add
> [    1.643333] bus: 'platform': add device atmel_usart_serial.1.auto
> [    1.643333] bus: 'platform': __driver_probe_device: matched device
> atmel_usart_serial.1.auto with driver atmel_usart_serial
> [    1.643333] bus: 'platform': really_probe: probing driver
> atmel_usart_serial with device atmel_usart_serial.1.auto
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no of_node;
> not parsing pinctrl DT
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no default
> pinctrl state
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: GPIO lookup
> for consumer rs485-term
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: using
> device tree for GPIO lookup
> [    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: using
> lookup tables for GPIO lookup
> [    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: No GPIO
> consumer rs485-term found
> [    1.649999] atmel_usart_serial.1.auto: ttyS2 at MMIO 0xf801c000 (irq
> = 24, base_baud = 8333333) is a ATMEL_SERIAL
> [    1.656666] driver: 'atmel_usart_serial': driver_bound: bound to
> device 'atmel_usart_serial.1.auto'
> [    1.656666] bus: 'platform': really_probe: bound device
> atmel_usart_serial.1.auto to driver atmel_usart_serial
> [    1.656666] driver: 'at91_usart_mode': driver_bound: bound to device
> 'f801c000.serial'
> [    1.656666] bus: 'platform': really_probe: bound device
> f801c000.serial to driver at91_usart_mode
> 
> [   41.606666] atmel_usart_serial atmel_usart_serial.1.auto: using
> dma0chan6 for rx DMA transfers
> [   41.613333] atmel_usart_serial atmel_usart_serial.1.auto: using
> dma0chan7 for tx DMA transfers
> 

What should I see in this log?

Thanks,
ta

[1] https://lore.kernel.org/lkml/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se/

> With kernel 4.5 spaces are there too, but shorter and less frequent.
> Thanks for any help,
> Jiri

Re: atmel usart and dma tx

[Tudor.Ambarus]

Hi, Jiří,

On 4/28/22 12:08, Jiří Prchal wrote:
> [Some people who received this message don't often get email from jiri.prchal@aksignal.cz. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
> 
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Hi everybody,
> with kernel 5.17, at91sam9g25 running at 400MHz I discovered drop outs
> while I write data (64 to 128B) to ttyS by one call of write(). At speed
> 230400 or 115200 Baud. It is not transmitted at once, there are random
> spaces long 200us to 1ms. It should use DMA so I think it could be
> transmitted at once.
> Is there everything OK with DMA or some special setting needed?

There are some concurrency problems with at-hdmac that happen at high
loads (check [1]), but I don't think it's related to your problem.
Can you do a flame graph to verify where in the code is the stall? Why
do you assume it's at the DMA level? Have you tried using usart without
DMA and verify if the stalling is still there?

> 
> dmesg:
> [    1.636666] bus: 'platform': __driver_probe_device: matched device
> f801c000.serial with driver at91_usart_mode
> [    1.636666] bus: 'platform': really_probe: probing driver
> at91_usart_mode with device f801c000.serial
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0-0: 2 0:0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function
> usart0 group usart0-0 num 3
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: usart0_rts-0: 1 0:2
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: maps: function
> usart0 group usart0_rts-0 num 2
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group
> selector 4 for usart0-0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: found group
> selector 5 for usart0_rts-0
> [    1.636666] at91_usart_mode f801c000.serial: no init pinctrl state
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function
> usart0 group usart0-0
> [    1.636666] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable function
> usart0 group usart0_rts-0
> [    1.639999] at91_usart_mode f801c000.serial: no sleep pinctrl state
> [    1.643333] at91_usart_mode f801c000.serial: no idle pinctrl state
> [    1.643333] Registering platform device 'atmel_usart_serial.1.auto'.
> Parent at f801c000.serial
> [    1.643333] device: 'atmel_usart_serial.1.auto': device_add
> [    1.643333] bus: 'platform': add device atmel_usart_serial.1.auto
> [    1.643333] bus: 'platform': __driver_probe_device: matched device
> atmel_usart_serial.1.auto with driver atmel_usart_serial
> [    1.643333] bus: 'platform': really_probe: probing driver
> atmel_usart_serial with device atmel_usart_serial.1.auto
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no of_node;
> not parsing pinctrl DT
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: no default
> pinctrl state
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: GPIO lookup
> for consumer rs485-term
> [    1.643333] atmel_usart_serial atmel_usart_serial.1.auto: using
> device tree for GPIO lookup
> [    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: using
> lookup tables for GPIO lookup
> [    1.646666] atmel_usart_serial atmel_usart_serial.1.auto: No GPIO
> consumer rs485-term found
> [    1.649999] atmel_usart_serial.1.auto: ttyS2 at MMIO 0xf801c000 (irq
> = 24, base_baud = 8333333) is a ATMEL_SERIAL
> [    1.656666] driver: 'atmel_usart_serial': driver_bound: bound to
> device 'atmel_usart_serial.1.auto'
> [    1.656666] bus: 'platform': really_probe: bound device
> atmel_usart_serial.1.auto to driver atmel_usart_serial
> [    1.656666] driver: 'at91_usart_mode': driver_bound: bound to device
> 'f801c000.serial'
> [    1.656666] bus: 'platform': really_probe: bound device
> f801c000.serial to driver at91_usart_mode
> 
> [   41.606666] atmel_usart_serial atmel_usart_serial.1.auto: using
> dma0chan6 for rx DMA transfers
> [   41.613333] atmel_usart_serial atmel_usart_serial.1.auto: using
> dma0chan7 for tx DMA transfers
> 

What should I see in this log?

Thanks,
ta

[1] https://lore.kernel.org/lkml/13c6c9a2-6db5-c3bf-349b-4c127ad3496a@axentia.se/

> With kernel 4.5 spaces are there too, but shorter and less frequent.
> Thanks for any help,
> Jiri

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel