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 C7330C4332F for ; Thu, 8 Dec 2022 17:06:33 +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=d7uDIZJGEw1hjxsR227SSONWWXA1b0X2k9094xYz5VQ=; b=Z0QYZr+g70Dtp2 VxSBVijYWNFUEWUoB/nr+uyB6ys46CiHR+TotfThJrz3IX7fT4oKdFZg4QTk3OeJO09gRvCEViNXQ EPP7h/NCf837RGhUSg/Lx6UPoqFm1vGyvBMNjbC7rlTyNO4Pk0ZvvAM7uTJaV0u00tt3eyRlhKDDM tQElX0DUgTITIanvoTWLv7cUwJep1xiTD28aqaxanlLrJtnaJwa6vgi9f815xvfCUeaN9gwXZUmCP QEWntLyisPflY39vA05OfeuBo0UgXBQrJPedbBgXRtGxj9/BU5sxABuemkBxQA1ui+CJsK6KdbcCM OBaA+v7suVmAATMTkqqQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3KKr-005sjU-J9; Thu, 08 Dec 2022 17:05:25 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3KKn-005sfQ-Ku for linux-arm-kernel@lists.infradead.org; Thu, 08 Dec 2022 17:05:23 +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 ams.source.kernel.org (Postfix) with ESMTPS id F2258B82568; Thu, 8 Dec 2022 17:05:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 592BDC433D2; Thu, 8 Dec 2022 17:05:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670519118; bh=mVa4rAGYCODwDCVnY1411oDOU/OwbCxVWI/1gCV76L4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=TVJAMl42DI3KGjqjl4yeG1Wb6wkYJ+HxG3Pl28rRAwWLrbFkeKsbGjSrXw5wYJOQw Va7W/v57CD8QmKvGBsWThaTFS4pyk5a+1NVSc7aAtlFJ1E4OvTcIYHgCy7d7qmudi/ 3gQ8Shs0AxWEmrIMBtlkjow+1GOdhiFcCuburUbDwqgbyB8bVD1mPo28Enl7zPXLXS MsGC7E63EqRyb7lYqZ5kNjZ+lqeWMomsNqaP/kdEtnS1RjIbrYeTzQCUyrQEmqdvPW mFrc5X3u9GoSuA1hlt9zsMVWCOOJPKw41Jp6cn1W0EQdRbtH/YAkEFWNa1XKIxj6UH f6stCSkh8wQYA== Date: Thu, 8 Dec 2022 09:05:17 -0800 From: Jakub Kicinski To: Jiri Pirko Cc: "Kubalewski, Arkadiusz" , Vadim Fedorenko , Jonathan Lemon , Paolo Abeni , "netdev@vger.kernel.org" , Vadim Fedorenko , linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, "Olech, Milena" , "Michalik, Michal" Subject: Re: [RFC PATCH v4 2/4] dpll: Add DPLL framework base functions Message-ID: <20221208090517.643277e8@kernel.org> In-Reply-To: References: <20221202212206.3619bd5f@kernel.org> <20221205161933.663ea611@kernel.org> <20221206092705.108ded86@kernel.org> <20221207085941.3b56bc8c@kernel.org> <20221208081955.335ca36c@kernel.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221208_090521_876775_78751C00 X-CRM114-Status: GOOD ( 12.81 ) 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 Thu, 8 Dec 2022 17:33:28 +0100 Jiri Pirko wrote: > For any synce pin manipulation over dpll netlink, we can use the netns > check of the linked netdev. This is the netns aware leg of the dpll, > it should be checked for. The OCP card is an atomic clock, it does not have any networking. > I can't imagine practically havind the whole dpll instance netns aware. > Omitting the fact that it really has no meaning for non-synce pins, what > would be the behaviour when for example pin 1 is in netns a, pin 2 in > netns b and dpll itself in netns c? To be clear I don't think it's a bad idea in general, I've done the same thing for my WIP PSP patches. But we already have one device without netdevs, hence I thought maybe devlink. So maybe we do the same thing with devlink? I mean - allow multiple devlink instances to be linked and require caps on any of them? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel