Received: by 10.223.176.5 with SMTP id f5csp2811852wra; Mon, 29 Jan 2018 04:29:31 -0800 (PST) X-Google-Smtp-Source: AH8x226L9OQkzICjjFDOXTTGV4lIX2/CxBdjcd8ilk9O9U4HSZT+RkECbsX1EZ33L8F+zx2UL+ce X-Received: by 2002:a17:902:8a4:: with SMTP id 33-v6mr18930948pll.279.1517228971174; Mon, 29 Jan 2018 04:29:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517228971; cv=none; d=google.com; s=arc-20160816; b=XA1KHfGU4SXh3lHvsz4YLx9g3btAf5VI/ctd3XQ+22qOohzWcLF6MMHP2Y3XXJa6c2 ONn0O22Q6TK2lX3cuHXQxixs5j+9bjPiLX3j1iN4brN8D43cQEYEd87E/8JD9lBT16Su D6hRkjIvXzWqq0ifE32TE4OZA0C5IS4WPEoPPQ8BafE9hHwcHtAk6ll/8PEqR9KKoJg5 ELgcAfMjA5onqjkvm+qOjqJ3HMCuo9DSYHAzjsAxyWTeQu0njEMfILt7rQ1fpws/mouL m010ZgMGv65hicdXWNnlQcIwxxDmZ5ZPY1OIWfaq2ZLN61U81QLtJRoAc+lcrRrPxjDf F7aA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=GQKt7rq50dN+sYDQP4B+hRzmwuvffDEJpOMx/P8pE8g=; b=lCgp7TsIrXP5wKk6YBIHNALPaMKkr54u4tRva/sadTCZcVNYkHdYSSAJgTw+DP8p+F wnjFT8+PZPzvPAqqYYP3VKG2EgyV1MO5RJZtN7CiKjLVHvOl4S2eWeB63ffm+Lnz2b3c e8tuuWvsj192q9ZsK1funMyXK66M9AB22KReRA8jplzwZ6+PqPRcnBkhCyhr/zZimcti eieuH0fICKMWJ/h429lBr/fEeIpN4azJ+NGop/NmWctepDOagusL63998KjbW7sfb02C ShK17Nstqpyko8JQ33OIbWG1v4AvWZiVTfoy0Q0h70eaZrXL+QXiofXj4Ng/JJ+1cJxl isYA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=MC+G8903; 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=NONE 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 z101-v6si4423515plh.596.2018.01.29.04.29.17; Mon, 29 Jan 2018 04:29:31 -0800 (PST) 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=MC+G8903; 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=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751885AbeA2M2x (ORCPT + 99 others); Mon, 29 Jan 2018 07:28:53 -0500 Received: from mail-io0-f196.google.com ([209.85.223.196]:43625 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751378AbeA2M2w (ORCPT ); Mon, 29 Jan 2018 07:28:52 -0500 Received: by mail-io0-f196.google.com with SMTP id 72so7400974iom.10 for ; Mon, 29 Jan 2018 04:28:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GQKt7rq50dN+sYDQP4B+hRzmwuvffDEJpOMx/P8pE8g=; b=MC+G8903zVEiAhqLqdqPjFvUxkDjdUouvKD6pZ120wYdKTVXrn4uq9xm/soMZ60t0w olME2KIj7ieFYGky935B88RSfUmMb4B3MyIZn41wqFHY9FuocqujCxj3M8fKPHFnzP9v QGgFUH+0AJtjVB1nanbQ++x64Uox09L5UJiS7MjTM7pP9eLNUScwj/tnuLNLkyVgkc9d XZ+MlC6/1tU7L3TczL/FnI2VoSewsBFFhd0seTxPYLF1uZ82JGSs7CG2xsGBb2xwA3Mi Uybkmn/553DVDYmftj9xthjK7ItpFzBrVq0Oa6803fqRBEFaSmFCF4TRj4Arwvs66EZ+ Mr9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GQKt7rq50dN+sYDQP4B+hRzmwuvffDEJpOMx/P8pE8g=; b=P7ET4VJ1g0kVNoY1xE+GSLCw5Rbh2Hpv/8n48+9lePhMnZvyxgVDnMsOwREsY6pVYg bnEwTS/WkQd0Yy2R812zxorZz7v89+dZOrx1IQFYwoIFS1+cdQZ2kDNUe+KHZptv0yzx 9w5ApNnydk1AQ6+UXpRBID3uOR8Km0LzngasDgXMRcZSHzSjXSzVMI8Ihxp54puAz4yh 0L6ohu5YAZVST+YtK9isEiHCrMVpJL0U8jIrT9x+u0mZQy1lH92++O7e5q+g6tcdkLYF TCBlQLi3o9/J01Vb02jRu3N2PrtWciHrnwrx5zLYzDElbOKquM27CzBYQbqlBcnt77Vg JvAw== X-Gm-Message-State: AKwxytfz7F6gghLlGgBKh4jXwcfTyyUs2H2QnwXCzZHrK/QltIGNor6e tPMUaaCQ7fFDSeOQ8Io0mqcMJeaLEhSA1ygP670= X-Received: by 10.107.157.131 with SMTP id g125mr11976800ioe.5.1517228932096; Mon, 29 Jan 2018 04:28:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.213.129 with HTTP; Mon, 29 Jan 2018 04:28:51 -0800 (PST) In-Reply-To: <20180129113248.GA10969@sirena.org.uk> References: <20180124141101.12867-1-codekipper@gmail.com> <20180124141101.12867-2-codekipper@gmail.com> <20180129113248.GA10969@sirena.org.uk> From: Code Kipper Date: Mon, 29 Jan 2018 13:28:51 +0100 Message-ID: Subject: Re: [linux-sunxi] [PATCH 1/3] ASoC: sun4i-i2s: Add set_tdm_slot functionality To: Mark Brown Cc: Chen-Yu Tsai , Maxime Ripard , linux-arm-kernel , linux-sunxi , Liam Girdwood , linux-kernel , Linux-ALSA , "Andrea Venturi (pers)" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29 January 2018 at 12:32, Mark Brown wrote: > On Mon, Jan 29, 2018 at 08:34:00AM +0100, Code Kipper wrote: > >> I'm not sure..I was looking for a clean example of being able to >> override the number of bclks in the lrclk width and some other >> devices(Rpi) were doing it this way. I open to suggestions, > > You're looking for set_bclk_ratio() I think. Hi Mark, I'm looking for a mechanism to be able to override the bclk width (usually it's based on param_width) from the device tree. The tdm slot functionality looked just what I needed. BR, CK