From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756872AbdJKLXS (ORCPT ); Wed, 11 Oct 2017 07:23:18 -0400 Received: from mail-wm0-f45.google.com ([74.125.82.45]:44975 "EHLO mail-wm0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751948AbdJKLXQ (ORCPT ); Wed, 11 Oct 2017 07:23:16 -0400 X-Google-Smtp-Source: AOwi7QCo6FP84bN5w+jwsLfYJZyKgKqvpC4PAzGLHW411HFRqcZTEMaRHhJex5RLz4I3wPQBhp6dJQ== Subject: Re: [alsa-devel] [Patch v6 1/7] slimbus: Device management on SLIMbus To: Vinod Koul Cc: gregkh@linuxfoundation.org, broonie@kernel.org, alsa-devel@alsa-project.org, mark.rutland@arm.com, michael.opdenacker@free-electrons.com, poeschel@lemonage.de, andreas.noever@gmail.com, gong.chen@linux.intel.com, arnd@arndb.de, kheitke@audience.com, bp@suse.de, devicetree@vger.kernel.org, james.hogan@imgtec.com, pawel.moll@arm.com, linux-arm-msm@vger.kernel.org, sharon.dvir1@mail.huji.ac.il, robh+dt@kernel.org, sdharia@codeaurora.org, alan@linux.intel.com, treding@nvidia.com, mathieu.poirier@linaro.org, jkosina@suse.cz, linux-kernel@vger.kernel.org, daniel@ffwll.ch, joe@perches.com, davem@davemloft.net References: <20171006155136.4682-1-srinivas.kandagatla@linaro.org> <20171006155136.4682-2-srinivas.kandagatla@linaro.org> <20171010104509.GC30097@localhost> <20171010164930.GD30097@localhost> <9e2bb2fa-b391-055e-407e-c93f43428840@linaro.org> <20171011040741.GE30097@localhost> <20171011102132.GG30097@localhost> From: Srinivas Kandagatla Message-ID: Date: Wed, 11 Oct 2017 12:23:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171011102132.GG30097@localhost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/10/17 11:21, Vinod Koul wrote: >>> ah which cases would those be. I was expecting that you would have a >>> platform_device as a slimbus controller which would call slim_register? >> As of now there is only one controller which uses platform driver, but in >> future there might be more, but this is something which makes the slimbus >> core more flexible. > even if you have more controllers wouldn't we have similar number of platform > devices. Each instance of the link/controller would have its device node. > Yep, I will give at try and see in next version! thanks, srini > Thanks > -- ~Vinod