Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755071AbcKNRiO (ORCPT ); Mon, 14 Nov 2016 12:38:14 -0500 Received: from mga11.intel.com ([192.55.52.93]:35157 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753757AbcKNRiM (ORCPT ); Mon, 14 Nov 2016 12:38:12 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,491,1473145200"; d="scan'208";a="191257919" Subject: Re: [alsa-devel] [RFC 09/14] SoundWire: Add support to handle Slave status change To: Charles Keepax , Hardik Shah References: <1477053673-16021-1-git-send-email-hardik.t.shah@intel.com> <1477053673-16021-10-git-send-email-hardik.t.shah@intel.com> <20161114160805.GO1575@localhost.localdomain> Cc: alsa-devel@alsa-project.org, tiwai@suse.de, plai@codeaurora.org, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, patches.audio@intel.com, broonie@kernel.org, Sanyog Kale From: Pierre-Louis Bossart Message-ID: <8f415778-f55a-3038-ec87-4b0ffea32b87@linux.intel.com> Date: Mon, 14 Nov 2016 11:38:08 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161114160805.GO1575@localhost.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 840 Lines: 16 On 11/14/16 10:08 AM, Charles Keepax wrote: > There are some issues with this, as the slave driver only probes > when the device actually shows up on the bus. However often > (especially in embedded contexts) some things may need to be > done to enable the slave. For example it may be held in reset or > its power supplies switched off until they are need. As such it > generally helps if the device probe can be called before it shows > up on the bus, the device probe can then do the necessary actions > to enable the device at which point it will show up on the bus. Yes, this point was made at the LPC miniconference. What's not clear to me is if you would want the codec driver to be notified that the bus is operational and let it handle things like sideband power management for that device, or is someone else needs to know.