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 X-Spam-Level: * X-Spam-Status: No, score=1.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, URIBL_DBL_ABUSE_MALW autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 80470C33CB3 for ; Sat, 1 Feb 2020 17:36:32 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 5750120678 for ; Sat, 1 Feb 2020 17:36:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="fnAryHeL"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="npYR5SuS" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5750120678 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject: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=jyjCKL9LABs4AIt4R1Ka9OlbZ7TvZgygHIXGlZ2Lu3o=; b=fnAryHeLNWDWmw 7k1eqd5lMC7W2K2fPf9MSjSUCkC4j/TOzi/Un5PMDS7t6XrQDzul/ezoMIGc2tS3MtMa+cIKayTCs BxsQFlsKJkZUms0wvIJszAIIBVk16jnGbJ9ZLpYFJpF15BPPvmqLBuR6krr7272JVDn2tWpLeFPoz v4nlGBPCJFGF32+DcunxVE3ojm8B5zfVSi+1R9B+1AWxaCnKdK/F0AAuOhhDLWJ1iCQ/efB8MCl4+ RkZFEqqYEf9ClEpg3WWNNKFSa2GNWpiul9FCgH16FE2aPYX88Hu3YAt54jHK7CVdnDIW/AcdopGQ8 JEovW7/FWuFYm9w1dOqQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1ixwh1-0003Iu-Sy; Sat, 01 Feb 2020 17:36:27 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1ixwgy-0003IU-4K for linux-arm-kernel@lists.infradead.org; Sat, 01 Feb 2020 17:36:25 +0000 Received: from cakuba.hsd1.ca.comcast.net (c-73-93-4-247.hsd1.ca.comcast.net [73.93.4.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3A7DC20678; Sat, 1 Feb 2020 17:36:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580578582; bh=KuaxtJRw14v59ff+I3CJb9O7IIbfHXwjQfiE5sV/mdE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=npYR5SuSSCd/RxiufbwuT5b4Zl8DzXdHMvm2gczI+LuLTrmyTyRHAxb8GqPRusVOi Nksy1LlWZ878WB0PdUdrVy/8Ii2I44Uj6dzZknH6IzTQTsdL+SqTTz+l5y69hwYEb7 /5shIJwIWw2mwK7nG7bHMe+sX4ZF1a4Tus98IhLg= Date: Sat, 1 Feb 2020 09:36:20 -0800 From: Jakub Kicinski To: Russell King - ARM Linux admin Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc Message-ID: <20200201093620.4b55d6fa@cakuba.hsd1.ca.comcast.net> In-Reply-To: <20200201114919.GQ25745@shell.armlinux.org.uk> References: <12531d6c569c7e14dffe8e288d9f4a0b@kernel.org> <0680c2ce-cff0-d163-6bd9-1eb39be06eee@arm.com> <20200131142906.GG9639@lunn.ch> <20200131151500.GO25745@shell.armlinux.org.uk> <20200131074050.38d78ff0@cakuba.hsd1.ca.comcast.net> <20200201114919.GQ25745@shell.armlinux.org.uk> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200201_093624_216526_DFA5A070 X-CRM114-Status: GOOD ( 13.78 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Andrew Lunn , Calvin Johnson , stuyoder@gmail.com, nleeder@codeaurora.org, Ioana Ciornei , Linux Kernel Mailing List , Cristi Sovaiala , Hanjun Guo , Will Deacon , Lorenzo Pieralisi , Marc Zyngier , Pankaj Bansal , Jon Nettleton , ACPI Devel Maling List , Len Brown , Jason Cooper , Andy Wang , Makarand Pawagi , Varun Sethi , Thomas Gleixner , linux-arm-kernel , Laurentiu Tudor , Paul Yang , Ard Biesheuvel , "" , "Rafael J. Wysocki" , Jiri Pirko , Shameerali Kolothum Thodi , Sudeep Holla , Robin Murphy Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sat, 1 Feb 2020 11:49:19 +0000, Russell King - ARM Linux admin wrote: > What if someone decides to do: > > devlink port split device/1 count 2 > > what do we end up with? Presumably two network devices running with > two serdes lanes each (if supported by the hardware). At that point > can they then do: > > devlink port split device/2 count 2 > > and end up with one network device with two 10G serdes lanes, and two > network devices each with one 10G serdes lane, I think all your guesses are correct, it's a pretty straight forward API, but it's also pretty thin, and some of the logic is in FW, so there isn't much in a way of a standard on how things should behave :S > or can port splitting only be used on the "master" device/port ? I think both mlxsw and the NFP rejects re-split/further splitting. Ports have to be unsplit first. So there is only one device for splitting, and unsplitting can be done on any of the sub-devices. > Unfortunately, I don't think I have any network devices that support > this so I can't experiment to find out how this should work; yes, I > have a Mellanox card, but it supports a single 10G SFP+, and therefore > does not support port splitting. I think you'd need a mlxsw or an nfp to play with this. Maybe Jiri can clarify further :) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel