Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6351607imu; Mon, 21 Jan 2019 07:27:33 -0800 (PST) X-Google-Smtp-Source: ALg8bN7HazhPIT3PXycy8bezwQ8nrrBSgkhn/6KZ5C2Cr0VDQxqpJoQD5RwDDEG9UydHmue8HMFV X-Received: by 2002:a63:6b05:: with SMTP id g5mr27785649pgc.15.1548084452982; Mon, 21 Jan 2019 07:27:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548084452; cv=none; d=google.com; s=arc-20160816; b=wItWo90iSnmpWi2rU0AwOacsWJxjzopZu+XxQh+lWPNj35R7J73wKVtjfw3bzyhxM/ JCBjuGHRvoIXefqq2kjtPBj20acjxV2XPA4kQpLBUOertPVF3FdcbwTfT1/AEj4NwqOu iWk4WxP0un2/H+Mhj8UxMHtvJPAJbxEjqSXD1T4rgiATIiB82+DsafMtOZOAlEzxocFk uyehPHLJWoHDiFlZNskBfeUS9vgAlS0aV8O9bAIQlAEZZTVYDBgmDp0xUJrjMBERqhPN X0DKfxnQpbIqIt55aPObVLgDuMTx8GnvIB/O+vrg+jgl4Tc4i3nrrk2Hg3FwZB+NQx7n XbUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=BTprJiQSSd9oFHbZyZXiPAZoKdv8sPvXoKx1czOhrmU=; b=aJd0IkpshCGR2SWMH5I1B82zf7aUkRa324myljhO8SUKFNKXijnZuTlnguH1n8vt9o caPlDO0rVyoUaYxSGGEeyBIz48Bh5xDPj1uxR8cyHZhDl9OzuaxV55Plt90JUOSBVhUU Yxqmva5YTKKudQVD1xNCRKWVVhOlYR1h5vqXPa9l2cUUcNku1nHmU9ey7NwpJ02bp+0a NXIiFLYGXzsdRg3RcIVcS7ETKquvhWFC123RVv+hdw8zva+hUMt0cG82ahJ8Xy01SYjH sAbtFsELXhlNGFrNxyZk1QxcFERLWc65v/77bAbaTtBIvSUntF4TO8alrJ3BJh868BQ6 Oe9w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b89si10946321pfj.207.2019.01.21.07.27.17; Mon, 21 Jan 2019 07:27:32 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730116AbfAUPXj (ORCPT + 99 others); Mon, 21 Jan 2019 10:23:39 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:45834 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730080AbfAUPXh (ORCPT ); Mon, 21 Jan 2019 10:23:37 -0500 Received: by mail-ot1-f66.google.com with SMTP id 32so20784805ota.12; Mon, 21 Jan 2019 07:23:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=BTprJiQSSd9oFHbZyZXiPAZoKdv8sPvXoKx1czOhrmU=; b=SF2/88uvEYmkjXxscUcv7ZE7xQ1gTC4jzQpsVTfZlk4ssZ2LOaC9LaAf+NJ47jfLY6 HC2nmtu9Oz6fFCbGJjzOF15qTIwe5qEuJi1WcrdzhRMWvWQBWUrXQL4um5QpQI78yoPI E8NYfU5cSwR33V/rgOMUS+4Stre8QoNp3MT13u64sKR27ojcZY0oVBOtAtr+6z25sSq9 GGXtPQJqgfln/YfIeKuRKvSy1vOKASJbphQbiZVeJSda3fxpXr4Kx5TtqYbiialevev8 HdgBiP0Agt4PcAd50fVYzfDfY8En6/alSkoQvrNCOOmXfiFOd4MOlOfjjOKotk8F7u4k CWjQ== X-Gm-Message-State: AJcUukfpZcJYBl/7WHdZXD7t/Dx9NF0f5MEPIfBHoz/PXzxftPzfv7DR LxEsPHVf+9OjjdFlZ1mB+kl3Q4c= X-Received: by 2002:a05:6830:1453:: with SMTP id w19mr14226713otp.213.1548084216296; Mon, 21 Jan 2019 07:23:36 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id i7sm5256034oth.57.2019.01.21.07.23.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 21 Jan 2019 07:23:35 -0800 (PST) Date: Mon, 21 Jan 2019 09:23:35 -0600 From: Rob Herring To: Nicolin Chen Cc: Viorel Suman , dl-linux-imx , Cosmin Samoila , "linux-kernel@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , "timur@kernel.org" , "devicetree@vger.kernel.org" , "Xiubo.Lee@gmail.com" , "viorel.suman@gmail.com" , Fabio Estevam , "broonie@kernel.org" , "mark.rutland@arm.com" , "tiwai@suse.com" , "lgirdwood@gmail.com" , "S.j. Wang" , Daniel Baluta , "perex@perex.cz" , "alsa-devel@alsa-project.org" Subject: Re: [PATCH v3 0/4] Add NXP AUDMIX device and machine drivers Message-ID: <20190121152335.GA12284@bogus> References: <1547729177-14317-1-git-send-email-viorel.suman@nxp.com> <20190117161804.GA5760@bogus> <1547817384.11482.33.camel@nxp.com> <20190118194642.GA11798@Asurada-Nvidia.nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190118194642.GA11798@Asurada-Nvidia.nvidia.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 18, 2019 at 11:46:42AM -0800, Nicolin Chen wrote: > On Fri, Jan 18, 2019 at 01:16:24PM +0000, Viorel Suman wrote: > > > > 1. Moved "dais" node from machine driver DTS node to device driver > > > > DTS node > > > > ? as suggested by Rob. > > > That was not what I suggested. You still have a virtual node which > > > looks to me to be unnecessary. > > > > To me removing virtual node implies that AUDMIX machine driver (imx- > > audmix.c + virtual node) shall be removed and machine driver code > > merged into device driver (fsl_audmix.c + device node) - please let me > > know if my understanding is wrong. > > We could use a non-DT configuration right? From the driver logic, > DT just registers a device corresponding to the machine driver so > that it can probe(). We could register one in fsl_audmix instead. > Please refer to how fsl_ssi registers the sound card device. The > machine driver can get audmix_np from the parent device pointer, > and I think that's all you need. Yes. > Or maybe someone else would provide a better way. But it'd work. Or the machine driver could create the audmix device. That probably makes less sense, but either way there doesn't have to be a 1-1 correspondence of DT nodes and (platform) devices. I'm not an ASoC expert, but why can't the machine driver just control the audmix directly (with DAIs as separate drivers)? Is the audmix ever going to a be a component for a different machine driver? Rob