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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BB032C77B7F for ; Fri, 5 May 2023 15:36:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=9HnDQOeyNFlJ5KxHcXqDFsrBFQmTR4NPko+cKXuh2aM=; b=4B9RtjSWDapNwk BZUuh9xxbepTd/ogYMDdIL3RKKer3Xt234v89VVoLXQD+KnS3V2khOzs/H3i+/DZG/rFJt96EAAuO c5rmcy3pH6JOHbGVZO13al+qi9pn9wrly+OjNZJ2oiPqQ0VkT6SM+H6EGqi0CVhmQaUGS1yd9uCSO Gea7r2ImPRC3eHR52HKCeT+/Vkyqu3NJkCDgpZ5xp/jx8fA7ZIoaO/uTkt4UUiR03+QO410q6qS7a ynVopH6djmUlo4MHtNDL5IDJzv4MvPJv0Nw9ELMIRSd2zWyMnRboAg0t589y35Ifn9BKYY6wgh7rl EgjBSwlZ4XB2r6wRwtOw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1puxT8-00BCmH-1m; Fri, 05 May 2023 15:35:38 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1puxT5-00BClO-0i for linux-arm-kernel@lists.infradead.org; Fri, 05 May 2023 15:35:36 +0000 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 dfw.source.kernel.org (Postfix) with ESMTPS id 757E463EE8; Fri, 5 May 2023 15:35:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BB4C9C433D2; Fri, 5 May 2023 15:35:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1683300933; bh=OPlunUdfvXK6uRgblU/QUedptc22mJhlsbSHxPNaQxs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=uBEgDxn0+0bsBQOFEUNODO6ici04abrkTGxM1Ti7VAM95VsgFk2A0hHDwHKCokrS8 Mrr294E3dvqDcIRNgYol1IsU5EujK8O1Bob44G/BGBu1hsfmNh4OBqj2ndi5SdVWqy 5iWznbzqTVUTHsSD+XIIkJg+XW8ORTejSLrh1Strkj5/sTefdvMAohby9eElUbrgUG 6LUZ7KNWtiZC0/ZLdYpG/hFQ69ZlV//oirR09L+2v9j879UzQBu50mA9hpFpZg0/YA mgu0x7txicTMdWoyqHeqjH9oSLXHR/AkaAr/aKKT00tmV6uZuyiVbQF7nc2upziaPW S07MJj9QPSIjw== Date: Fri, 5 May 2023 08:35:31 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: "Kubalewski, Arkadiusz" , Vadim Fedorenko , Vadim Fedorenko , Jonathan Lemon , Paolo Abeni , poros , mschmidt , "netdev@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, "linux-clk@vger.kernel.org" , "Olech, Milena" , "Michalik, Michal" Subject: Re: [PATCH RFC v6 2/6] dpll: Add DPLL framework base functions Message-ID: <20230505083531.57966958@kernel.org> In-Reply-To: References: <20230417124942.4305abfa@kernel.org> <20230502083244.19543d26@kernel.org> <20230503191643.12a6e559@kernel.org> <20230504090401.597a7a61@kernel.org> <20230504114421.51415018@kernel.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230505_083535_313269_FB90552E X-CRM114-Status: GOOD ( 16.02 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 5 May 2023 12:41:11 +0200 Jiri Pirko wrote: > >connector label (i.e. front panel label)? Or also applicable to > >internal pins? It'd be easier to talk details if we had the user > >facing documentation that ships with these products. > > I think is is use case specific. Some of the pins face the user over > physical port, they it is a front panel label. Others are internal > names. I have no clue how to define and mainly enforce rules here. It should be pretty easy to judge if we see the user-facing documentation vendors have. > But as an example, if you have 2 pins of the same type, only difference > is they are connected to front panel connector "A" and "B", this is the > label you have to pass to the ID query. Do you see any other way? Sound perfectly fine, if it's a front panel label, let's call the attribute DPLL_A_PIN_FRONT_PANEL_LABEL. If the pin is not brought out to the front panel it will not have this attr. For other type of labels we should have different attributes. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel