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 4BE55EB64DD for ; Sat, 22 Jul 2023 02:09:01 +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=JIWz3lF2Gj7prD3sUOKf0xf8LNtgT8bsTUklU4DF6Ec=; b=AXRYBrBe4O/W4p 3/U17H8KFpC8Xxrnjsmbh3l/qHg4D5PksMtYc7Ukf9BcNEEeGooVl7HPSA5ukxZDhJL0u471cI32v zgHnf3QkPguq1+uNgbNDsE6T/ULGfp44X1mPemDORPXHU19E4whjbUrNi2ovtMefZfKd33qHwrbbf P+QoDQza987OVwNiCQmGvzH/PDc9lkB5NOWskWWXwNjMAhOwz+6RBK6FAJUfQuYG2wncmulvG+YEN smH3UmejRVv4FSJcgE/t5B5MYs4E9ClhnK2bpZ54n2TekDO0dWStTVhpA/EFjCJjUmtL4PPANV8eh mrGUm4v6tUXBNGHALk7A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qN230-00FacI-1J; Sat, 22 Jul 2023 02:08:42 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qN22x-00Fabi-2S for linux-arm-kernel@lists.infradead.org; Sat, 22 Jul 2023 02:08:40 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6B27A61DBC; Sat, 22 Jul 2023 02:08:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4B441C433C7; Sat, 22 Jul 2023 02:08:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689991715; bh=9NGLbvUwwVAcvCYY973O4b6WDduuentH0GBBnEGBEjk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=AlMhkIbLgYxczvUbEIs65r6z2G26WTaynmjVeFpH9To5eyI2SkBfTnuGtaA4KKdcO FBQLWKP+x7nLBxc4fosekBHr+8Us9J6YCsBbODXPdBaWt6RBqydCQTGDXeQGgqqgKz kLKuzk0DDq3KGIUJxRw8ahKvO9perKPLATJhgiMI9QIbhygni+vamJGo29+yJtoBqF /8/MoDlY3RgnPhfNlQl8K9nC1TQjv5lPqKrAzeTEeH88LC5wewXa97zbfBRnFnyqGB 5EoT8+iDCq8a8uPTNOsa3zLx7d6MF64ZcOh/8hyErWqfYObChp2A13b01mKxYoGEhi q1PesA+s/3oNw== Date: Fri, 21 Jul 2023 19:08:34 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: "Kubalewski, Arkadiusz" , Vadim Fedorenko , Jonathan Lemon , Paolo Abeni , "Olech, Milena" , "Michalik, Michal" , "linux-arm-kernel@lists.infradead.org" , poros , mschmidt , "netdev@vger.kernel.org" , "linux-clk@vger.kernel.org" , Bart Van Assche Subject: Re: [PATCH 09/11] ice: implement dpll interface to control cgu Message-ID: <20230721190834.375dbb79@kernel.org> In-Reply-To: References: <20230720091903.297066-1-vadim.fedorenko@linux.dev> <20230720091903.297066-10-vadim.fedorenko@linux.dev> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230721_190839_840008_550BE2EA X-CRM114-Status: GOOD ( 13.13 ) 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, 21 Jul 2023 09:33:14 +0200 Jiri Pirko wrote: > >d) SyncE daemon uses PIN_SET to set state of pin_id:13 to CONNECTED with > > parent pin (pin-id:2) > > For this you need pin_id and pin_parent_id because you set the state on > a parent pin. > > > Yeah, this is exactly why I initially was in favour of hiding all the > muxes and magic around it hidden from the user. Now every userspace app > working with this has to implement a logic of tracking pin and the mux > parents (possibly multiple levels) and configure everything. But it just > need a simple thing: "select this pin as a source" :/ > > > Jakub, isn't this sort of unnecessary HW-details complexicity exposure > in UAPI you were against in the past? Am I missing something? >From just reading what I'm quoting - I don't think so. Muxes are meaningful because they limit valid configurations. We can implement "automatic mutex config" in the kernel if user wants it, centrally in the core, otherwise each driver will have to do it on its own. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel