Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4244782imu; Tue, 18 Dec 2018 11:24:13 -0800 (PST) X-Google-Smtp-Source: AFSGD/XM4UbcVMiEWX5JQC7zGwIB/VClZQDB5TYZVEPbqOLT8aabZzVTjolm575hnQIzrzp8+xFn X-Received: by 2002:a63:2406:: with SMTP id k6mr16311779pgk.229.1545161053186; Tue, 18 Dec 2018 11:24:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545161053; cv=none; d=google.com; s=arc-20160816; b=kXKzsrP4pqkhdOnwlxxRJwuka+wPDJpDjUVSTZTmr6YuR5YyfqahverGY683ddAywv pLGqUep0SKt0P2jY2KhCFxs3K/vSp7dmT1N1KBbQbXq3Ds66XxLTEwNAI3Hja7S4J1Gj /zIC6QH8Ah7LPtq2xpqBeZsXXpL2XR0jiqpAKmR5UJKvWKCRkXt5UxzGqCVY3EVIaCAp 7Ve7Y2LstHIfIznmN0DTBZW/uvIBl6waobfvc4YNPp+xQKmu0oaJBdVSxT0uLC4+qgfm boAClobi1oC9coTGUxTus8AkIcZhM8yxPBIOwQuttiMErYkaqmGVXSehKmaZTgbeDVhF eKMA== 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-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=NMzcuZQjcluVah8TenQKral9o/O1+dIJaTL7AwYbMpM=; b=eH1jqn9qUezZ6aedtxYJrxDjyZmFGZ6LYd6pTsEA7XpKjnP+to01unMKatPRY8ohcc 8rO18putXFQb70qAYqPfFXVvw0vDS2GrRIG4h4Ez9hH97BtXf8vWbXl6u5sEk3H6/R3U flXWPkFzegGRA2X/t06qYtKv3kxIfFLB+LxKYoE7bVyuDLZyEB2Wisu+KU211GdGbHb2 /qhIs1FfleaCF881oRkK+cgwVS3Oxiht/7lIBxbeQ+kqPOm87YsmjXNWY/MMiPA6VI0d T6xwd/Abln4prmbwpKxbZ1h0sMlqmpVnSzU5TrWp/R9Ob3gevkNPccx4C1lWLpGigRaj m3Tg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@horus.com header.s=20180324 header.b=JE+zqLgi; 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=horus.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x10si5347447pgl.209.2018.12.18.11.23.57; Tue, 18 Dec 2018 11:24:13 -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=@horus.com header.s=20180324 header.b=JE+zqLgi; 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=horus.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727365AbeLRRrQ (ORCPT + 99 others); Tue, 18 Dec 2018 12:47:16 -0500 Received: from mail.horus.com ([78.46.148.228]:41543 "EHLO mail.horus.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726659AbeLRRrQ (ORCPT ); Tue, 18 Dec 2018 12:47:16 -0500 X-Greylist: delayed 392 seconds by postgrey-1.27 at vger.kernel.org; Tue, 18 Dec 2018 12:47:14 EST Received: from [192.168.1.20] (62-47-205-9.adsl.highway.telekom.at [62.47.205.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "E-Mail Matthias Reichl", Issuer "HiassofT CA 2014" (verified OK)) by mail.horus.com (Postfix) with ESMTPSA id 705B7641D9; Tue, 18 Dec 2018 18:40:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=horus.com; s=20180324; t=1545154841; bh=NMzcuZQjcluVah8TenQKral9o/O1+dIJaTL7AwYbMpM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=JE+zqLgiemWwkHaB3yGSuCEshBTtevwRa6ktWnjfDGLED7RH1B3F3XGZGUQ845fvF YNMEmvcFRDGxI/BlC6hUwB0csJAQBlIXwyNzxJ9zglTiE2QmSsGqsdjiGlqFyUr6YU FbGhiDW5GFd6kWrzr4tlqnmrtaw3UGuJsAj9HUdw= Received: by camel2.lan (Postfix, from userid 1000) id C67941C72A2; Tue, 18 Dec 2018 18:40:40 +0100 (CET) Date: Tue, 18 Dec 2018 18:40:40 +0100 From: Matthias Reichl To: Mark Brown Cc: Jon Hunter , alsa-devel@alsa-project.org, Kuninori Morimoto , Liam Girdwood , Marcel Ziswiler , Takashi Iwai , linux-kernel@vger.kernel.org, Marcel Ziswiler , linux-tegra@vger.kernel.org Subject: Re: [alsa-devel] [PATCH v1 3/3] ASoC: soc-core: fix platform name vs. of_node assignement Message-ID: <20181218174040.k7u26vnnoplllnwb@camel2.lan> Mail-Followup-To: Matthias Reichl , Mark Brown , Jon Hunter , alsa-devel@alsa-project.org, Kuninori Morimoto , Liam Girdwood , Marcel Ziswiler , Takashi Iwai , linux-kernel@vger.kernel.org, Marcel Ziswiler , linux-tegra@vger.kernel.org References: <20181018111829.27056-1-marcel@ziswiler.com> <20181018111829.27056-4-marcel@ziswiler.com> <20181021112301.GC8554@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181021112301.GC8554@sirena.org.uk> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, On Sun, Oct 21, 2018 at 12:23:01PM +0100, Mark Brown wrote: > On Fri, Oct 19, 2018 at 11:22:46AM +0100, Jon Hunter wrote: > > > Looking at snd_soc_init_platform(), it seems that the platform pointer > > can be allocated by the machine driver and so if it is not allocated by > > the core, then I don't think we should clear it here. Seems we need a > > way to determine if this was allocated by the core. > > Indeed, this is a bit of a mess. We probably shouldn't be modifying the > data that the drivers passed in, otherwise we get into trouble like > this. That suggests that we should copy the data, probably all of it. > I will try to have a proper look at this next week. did you find the time to look into this? The downstream Raspberry Pi kernel contains a bunch of machine drivers that are implemented in a similar way as the tegra_sgtl5000 driver (static card and dai link structs, dai_link->platform_of_node filled in from device tree) which are breaking in 4.20 on deferred probing. Switching these drivers to dynamically allocated dai link structs, like 76836fd35492 "ASoC: omap-abe-twl6040: Fix missing audio card caused by deferred probing" would be a possibility, but if there's some solution on the horizon that doesn't require changes to the driver code it'd be easier to wait for that. so long, Hias > > Furthermore, it seems that it is possible that there is more than one > > link that might be to be cleared. > > Yes, that's an issue as well. > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel