Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp4966013ybi; Tue, 30 Jul 2019 11:16:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqzu4NtQGOtzpJlrprwVoNiXk7ryorusdXo2laWHfTt6t5b12yq6740IZkp8gFKh0zB2a+6E X-Received: by 2002:a17:90a:1aa4:: with SMTP id p33mr120071009pjp.27.1564510599843; Tue, 30 Jul 2019 11:16:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564510599; cv=none; d=google.com; s=arc-20160816; b=eDN2VOmLGKOgyR26dVf+VRQJtbM56Fzctn3yLubI78dafZbgk4FWLrR1/fkQ/xdP3T R3P06V5sWpdPHCZDaSnV5VX/TIER0lByIRv7mnnucs5KiVmwF2l0ojQgR51hzKXIFMMQ lzsy4mXeXMl/Y6wHgIEWWQ8lf5h1VzqNwHCCA2woMqGuG5IsvAFYUgIF5PXCxvx7fEdr lkV6DdzwjfyluTqHK4Hd0ca5m8WErq3VqdG9cE6LYWud+PZDRUyG62rGwjPnNCKDalNO GBkfhtjHEYl/d86alEOEmV8j/2jaXoqdMRZ9YKj1LviX+7InrQFI6lFgVXD02NpkP8fN dUyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=i9gr1REy9uU6tIvdybdq1wzB3yKSOtp91cfB88+O2No=; b=PiObQ1xqr+w/+a56V9UUdZZnNJslpUKbpce/HLJm6dLamuqfCjeDvVehe32Wee3/G2 eF/jcT8wnz3Z0AzajUz2jKhTHAZ8KTXFxM4Mq7t+WKYjl63R7CWZ0zimg72uw3VejqT+ 2ALqNx4F8nqzEba3M0x0WTZQIH31jbHamYyGOfqZ/QVLyzUqWYM/9U9dWQJGCpXm6Oc5 tlna+HftktOxcqoyNnZ8oGVy8cYhZWcKK+H5J/DDKkSJuf1YKHne9KawuUNJf++yZZYi 52IvCn3EVqYoXzVxoXKPVSa91tPSxdm64LIA0OiPUG4RV6ngoFSfpn/WDAeGIl101Z4Q f/tg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Y6M7AaP5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t13si30180685pfh.245.2019.07.30.11.16.24; Tue, 30 Jul 2019 11:16:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Y6M7AaP5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387591AbfG3R5R (ORCPT + 99 others); Tue, 30 Jul 2019 13:57:17 -0400 Received: from mail-wr1-f65.google.com ([209.85.221.65]:40148 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387552AbfG3R5Q (ORCPT ); Tue, 30 Jul 2019 13:57:16 -0400 Received: by mail-wr1-f65.google.com with SMTP id r1so66730803wrl.7 for ; Tue, 30 Jul 2019 10:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=i9gr1REy9uU6tIvdybdq1wzB3yKSOtp91cfB88+O2No=; b=Y6M7AaP5KZ0RlOVpdvuT71waGZaMGFG7LB6Ue/fz3whPZ/OM1Dol+xR5rhWZOUaYDB 3oQgI3oYF8IxRB2eIavbT1IJ0lb3lwl3dOLfpkn1iFRigKgsp2/XlQd2cN/T/qx7vqxT oCMq238bpwZann7Ow8V9o5QUcYgwVAbTj2qXdhKV1c2lKohoGhBQ9EB4iZqo94uB8pX0 rPMFEmyyqTRG9EXWylTjZmzluhiTTTkWlifiadyF9F0rCK+JEyWZ4bDE7SVvU3Wv6ztQ bQIsxeeoi6TgMXwvrb1JPtat1HV0VCBwNaXikDdmW9GckY7k3Bf7iLs7SggiNHxUcLLF OHYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=i9gr1REy9uU6tIvdybdq1wzB3yKSOtp91cfB88+O2No=; b=SvuNbgzjXKdMiC6dAmiqJMB6ieWFYQBOUHmKcao+mr6620WitE8O4gIrxxUyOsrho6 k21EHkk4DcG/y+drjdoY3DFWgbg33P5Me3jafEPPhX/jrjMEKN6TjBEhzSI1FeE683eX Fj1S1HOrOMNB46GGhEnTWGnrISoF+O/akyG9RFH6Y2ZPKT0Uluxix1ow1+/fwcQJjxXk VoMYOQdNZg5udtY0Pqfi299FGXLFmMcQgnuRoItfjxqaMhLbtnRN94DhVmB5Z5oGajUf YEtzJaOh18IkiY1BWdvvYjNjPy2UfeznccdnF5nUWrI5X85hO0MZTdUe9vxZlvMje96r YgMw== X-Gm-Message-State: APjAAAWtIeh7tqHKXL6jAF3N3F0rjS1T11WGIwrcplNa3gAk/oJwos15 q/0qfYnLiU98F9qdN0mbX30= X-Received: by 2002:adf:f005:: with SMTP id j5mr80353105wro.251.1564509433345; Tue, 30 Jul 2019 10:57:13 -0700 (PDT) Received: from jernej-laptop.localnet (cpe-194-152-11-237.cable.triera.net. [194.152.11.237]) by smtp.gmail.com with ESMTPSA id a84sm82098514wmf.29.2019.07.30.10.57.11 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 30 Jul 2019 10:57:12 -0700 (PDT) From: Jernej =?utf-8?B?xaBrcmFiZWM=?= To: linux-sunxi@googlegroups.com, codekipper@gmail.com Cc: Christopher Obbard , Maxime Ripard , Chen-Yu Tsai , linux-arm-kernel , Liam Girdwood , Mark Brown , linux-kernel , Linux-ALSA , "Andrea Venturi (pers)" Subject: Re: [linux-sunxi] Re: [PATCH v4 6/9] ASoC: sun4i-i2s: Add multi-lane functionality Date: Tue, 30 Jul 2019 19:57:10 +0200 Message-ID: <2092329.vleAuWJ0xl@jernej-laptop> In-Reply-To: References: <20190603174735.21002-1-codekipper@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! Dne torek, 04. junij 2019 ob 11:38:44 CEST je Code Kipper napisal(a): > On Tue, 4 Jun 2019 at 11:02, Christopher Obbard wrote: > > On Tue, 4 Jun 2019 at 09:43, Code Kipper wrote: > > > On Tue, 4 Jun 2019 at 09:58, Maxime Ripard wrote: > > > > On Mon, Jun 03, 2019 at 07:47:32PM +0200, codekipper@gmail.com wrote: > > > > > From: Marcus Cooper > > > > > > > > > > The i2s block supports multi-lane i2s output however this > > > > > functionality > > > > > is only possible in earlier SoCs where the pins are exposed and for > > > > > the i2s block used for HDMI audio on the later SoCs. > > > > > > > > > > To enable this functionality, an optional property has been added to > > > > > the bindings. > > > > > > > > > > Signed-off-by: Marcus Cooper > > > > > > > > I'd like to have Mark's input on this, but I'm really worried about > > > > the interaction with the proper TDM support. > > > > > > > > Our fundamental issue is that the controller can have up to 8 > > > > channels, but either on 4 lines (instead of 1), or 8 channels on 1 > > > > (like proper TDM) (or any combination between the two, but that should > > > > be pretty rare). > > > > > > I understand...maybe the TDM needs to be extended to support this to > > > consider channel mapping and multiple transfer lines. I was thinking > > > about the later when someone was requesting support on IIRC a while > > > ago, I thought masking might of been a solution. These can wait as the > > > only consumer at the moment is LibreELEC and we can patch it there. > > > > Hi Marcus, > > > > FWIW, the TI McASP driver has support for TDM & (i think?) multiple > > transfer lines which are called serializers. > > Maybe this can help with inspiration? > > see > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/s > > ound/soc/ti/davinci-mcasp.c sample DTS: > > > > &mcasp0 { > > > > #sound-dai-cells = <0>; > > status = "okay"; > > pinctrl-names = "default"; > > pinctrl-0 = <&mcasp0_pins>; > > > > op-mode = <0>; > > tdm-slots = <8>; > > serial-dir = < > > > > 2 0 1 0 > > 0 0 0 0 > > 0 0 0 0 > > 0 0 0 0 > > > > > >; > > > > tx-num-evt = <1>; > > rx-num-evt = <1>; > > > > }; > > > > > > Cheers! > > Thanks, this looks good. I would really like to see this issue resolved, because HDMI audio support in mainline Linux for those SoCs is long overdue. However, there is a possibility to still add HDMI audio suport (stereo only) even if this issue is not completely solved. If we agree that configuration of channels would be solved with additional property as Christopher suggested, support for >2 channels can be left for a later time when support for that property would be implemented. Currently, stereo HDMI audio support can be added with a few patches. I think all I2S cores are really the same, no matter if internally connected to HDMI controller or routed to pins, so it would make sense to use same compatible for all of them. It's just that those I2S cores which are routed to pins can use only one lane and >2 channels can be used only in TDM mode of operation, if I understand this correctly. New property would have to be optional, so it's omission would result in same channel configuration as it is already present, to preserve compatibility with old device trees. And this mode is already sufficient for stereo HDMI audio support. Side note: HDMI audio with current sun4i-i2s driver has a delay (about a second), supposedly because DW HDMI controller automatically generates CTS value based on I2S clock (auto CTS value generation is enabled per DesignWare recomendation for DW HDMI I2S interface). I2S driver from BSP Linux solves that by having I2S clock output enabled all the time. Should this be flagged with some additional property in DT? Best regards, Jernej > CK > > > > Do you have any ideas Master? > > > CK > > > > > > > You're trying to do the first one, and I'm trying to do the second > > > > one. > > > > > > > > There's a number of assumptions later on that will break the TDM case, > > > > see below for examples > > > > > > > > > --- > > > > > > > > > > sound/soc/sunxi/sun4i-i2s.c | 44 > > > > > ++++++++++++++++++++++++++++++++----- > > > > > 1 file changed, 39 insertions(+), 5 deletions(-) > > > > > > > > > > diff --git a/sound/soc/sunxi/sun4i-i2s.c > > > > > b/sound/soc/sunxi/sun4i-i2s.c > > > > > index bca73b3c0d74..75217fb52bfa 100644 > > > > > --- a/sound/soc/sunxi/sun4i-i2s.c > > > > > +++ b/sound/soc/sunxi/sun4i-i2s.c > > > > > @@ -23,7 +23,7 @@ > > > > > > > > > > #define SUN4I_I2S_CTRL_REG 0x00 > > > > > #define SUN4I_I2S_CTRL_SDO_EN_MASK GENMASK(11, 8) > > > > > > > > > > -#define SUN4I_I2S_CTRL_SDO_EN(sdo) BIT(8 + (sdo)) > > > > > +#define SUN4I_I2S_CTRL_SDO_EN(lines) (((1 << lines) - 1) << > > > > > 8) > > > > > > > > > > #define SUN4I_I2S_CTRL_MODE_MASK BIT(5) > > > > > #define SUN4I_I2S_CTRL_MODE_SLAVE (1 << 5) > > > > > #define SUN4I_I2S_CTRL_MODE_MASTER (0 << 5) > > > > > > > > > > @@ -355,14 +355,23 @@ static int sun4i_i2s_hw_params(struct > > > > > snd_pcm_substream *substream,> > > > > > > > > struct sun4i_i2s *i2s = snd_soc_dai_get_drvdata(dai); > > > > > int sr, wss, channels; > > > > > u32 width; > > > > > > > > > > + int lines; > > > > > > > > > > channels = params_channels(params); > > > > > > > > > > - if (channels != 2) { > > > > > + if ((channels > dai->driver->playback.channels_max) || > > > > > + (channels < dai->driver->playback.channels_min)) { > > > > > > > > > > dev_err(dai->dev, "Unsupported number of channels: > > > > > %d\n", > > > > > > > > > > channels); > > > > > > > > > > return -EINVAL; > > > > > > > > > > } > > > > > > > > > > + lines = (channels + 1) / 2; > > > > > + > > > > > + /* Enable the required output lines */ > > > > > + regmap_update_bits(i2s->regmap, SUN4I_I2S_CTRL_REG, > > > > > + SUN4I_I2S_CTRL_SDO_EN_MASK, > > > > > + SUN4I_I2S_CTRL_SDO_EN(lines)); > > > > > + > > > > > > > > This has the assumption that each line will have 2 channels, which is > > > > wrong.> > > > > > > > if (i2s->variant->is_h3_i2s_based) { > > > > > > > > > > regmap_update_bits(i2s->regmap, > > > > > SUN8I_I2S_CHAN_CFG_REG, > > > > > > > > > > SUN8I_I2S_CHAN_CFG_TX_SLOT_NUM_MASK > > > > > , > > > > > > > > > > @@ -373,8 +382,19 @@ static int sun4i_i2s_hw_params(struct > > > > > snd_pcm_substream *substream,> > > > > > > > > } > > > > > > > > > > /* Map the channels for playback and capture */ > > > > > > > > > > - regmap_field_write(i2s->field_txchanmap, 0x76543210); > > > > > > > > > > regmap_field_write(i2s->field_rxchanmap, 0x00003210); > > > > > > > > > > + regmap_field_write(i2s->field_txchanmap, 0x10); > > > > > + if (i2s->variant->is_h3_i2s_based) { > > > > > + if (channels > 2) > > > > > + regmap_write(i2s->regmap, > > > > > + SUN8I_I2S_TX_CHAN_MAP_REG+4, > > > > > 0x32); > > > > > + if (channels > 4) > > > > > + regmap_write(i2s->regmap, > > > > > + SUN8I_I2S_TX_CHAN_MAP_REG+8, > > > > > 0x54); > > > > > + if (channels > 6) > > > > > + regmap_write(i2s->regmap, > > > > > + SUN8I_I2S_TX_CHAN_MAP_REG+12, > > > > > 0x76); > > > > > + } > > > > > > > > And this creates a mapping matching that. > > > > > > > > > /* Configure the channels */ > > > > > regmap_field_write(i2s->field_txchansel, > > > > > > > > > > @@ -1057,9 +1077,10 @@ static int > > > > > sun4i_i2s_init_regmap_fields(struct device *dev,> > > > > > > > > static int sun4i_i2s_probe(struct platform_device *pdev) > > > > > { > > > > > > > > > > struct sun4i_i2s *i2s; > > > > > > > > > > + struct snd_soc_dai_driver *soc_dai; > > > > > > > > > > struct resource *res; > > > > > void __iomem *regs; > > > > > > > > > > - int irq, ret; > > > > > + int irq, ret, val; > > > > > > > > > > i2s = devm_kzalloc(&pdev->dev, sizeof(*i2s), GFP_KERNEL); > > > > > if (!i2s) > > > > > > > > > > @@ -1126,6 +1147,19 @@ static int sun4i_i2s_probe(struct > > > > > platform_device *pdev)> > > > > > > > > i2s->capture_dma_data.addr = res->start + > > > > > SUN4I_I2S_FIFO_RX_REG; > > > > > i2s->capture_dma_data.maxburst = 8; > > > > > > > > > > + soc_dai = devm_kmemdup(&pdev->dev, &sun4i_i2s_dai, > > > > > + sizeof(*soc_dai), GFP_KERNEL); > > > > > + if (!soc_dai) { > > > > > + ret = -ENOMEM; > > > > > + goto err_pm_disable; > > > > > + } > > > > > + > > > > > + if (!of_property_read_u32(pdev->dev.of_node, > > > > > + "allwinner,playback-channels", > > > > > &val)) { > > > > > + if (val >= 2 && val <= 8) > > > > > + soc_dai->playback.channels_max = val; > > > > > + } > > > > > + > > > > > > > > I'm not quite sure how this works. > > > > > > > > of_property_read_u32 will return 0, so you will enter in the > > > > condition. But what happens if the property is missing? > > > > > > > > Maxime > > > > > > > > -- > > > > Maxime Ripard, Bootlin > > > > Embedded Linux and Kernel engineering > > > > https://bootlin.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+unsubscribe@googlegroups.com. To view this discussion on > > > the web, visit > > > https://groups.google.com/d/msgid/linux-sunxi/CAEKpxB%3DRdYF9eEvAJ%2BR7 > > > sT6OtdtBWjhMM1am%2BEhaN%3D9ZO9Gd2A%40mail.gmail.com. For more options, > > > visit https://groups.google.com/d/optout.