From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C54ABC32772 for ; Tue, 23 Aug 2022 18:38:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230191AbiHWSiE (ORCPT ); Tue, 23 Aug 2022 14:38:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232798AbiHWShi (ORCPT ); Tue, 23 Aug 2022 14:37:38 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 09920112C5F for ; Tue, 23 Aug 2022 10:00:29 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 701BBB81E97 for ; Tue, 23 Aug 2022 17:00:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A3BCCC433D6; Tue, 23 Aug 2022 17:00:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661274027; bh=d+UO5JCLB6pOQQecPBJTnPqg/phJ8oDfkjxDgPpU78M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dWGbMRp6InFfgbZqiXs/vb/mHcDhH1LHqnOYHw8dNY3Xl58QBc8nSYOZQm4YYnMVo nkaL7e2XtTTDlRkLD5ZB4LUX/SoNPCNdmfbnF4ZLVf3ug7pmzTByhfDAgnoPfhrbrx Rij1uPC7arGaxcC6UOLMLyrluOHs6QVHY/F9YHiijb12ayaqo/SnMdztWZjZvv8ucP Zg/1Oe34+GrYSgXc8yEYaHpNhK7TEZR6tVJW9EYagtRc8c3k2csTnCQfutdHb1WuQy Pi8c/zgzjqQH8TTxkG/8Mx2d5Pcvt1AGiBTvPvH/5/+yfVoO27TpsSXGb5IECpj19u h7C5Z7OiCU+rw== Date: Tue, 23 Aug 2022 22:30:23 +0530 From: Vinod Koul To: Bard Liao Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, pierre-louis.bossart@linux.intel.com, bard.liao@intel.com Subject: Re: [PATCH 0/3] soundwire: allocate device_number with IDA Message-ID: References: <20220823045004.2670658-1-yung-chuan.liao@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220823045004.2670658-1-yung-chuan.liao@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23-08-22, 12:50, Bard Liao wrote: > The device_number is currently allocated in the scope of each bus and does > not need to be unique at the system level. > This leads e.g. on Dell devices with three or four Device1 on different > bus segments. And how is that an issue that should be fixed? > To make the device_number unique at the system level, and Why should we do that... > unified with the HDaudio/iDISP SDI values, this series allocates the > dev_number with an IDA restricted between 4 and 11 (inclusive). Does this not place an artificial restriction that a system can have only 12 devices if we have unique device Perhaps a better way would be to use dus:dev combination while dealing with a device always..?? -- ~Vinod