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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (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 89340CDB482 for ; Fri, 13 Oct 2023 23:45:16 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=pcbMzY+n; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4S6jmW1Y89z3vjV for ; Sat, 14 Oct 2023 10:45:15 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=pcbMzY+n; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=kuba@kernel.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4S6jkp4JMdz3vYp for ; Sat, 14 Oct 2023 10:43:46 +1100 (AEDT) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 760D562202; Fri, 13 Oct 2023 23:43:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AF660C433C8; Fri, 13 Oct 2023 23:43:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697240624; bh=XMsp3WQfHWzYrvwTL5bSfSAdHyGXuKsHrx4YecNlQnQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=pcbMzY+nvNyIhtSC8ysJbc2lzO4vgdQ56KyCMQKjQkGDFWlLd84I9WSAIk4Jm+sNj smTiXtjEjWCCCx0X3mCBp4QP6yqvUGQ4GFZsJj4MG4B82xN2as+zaYRQVor7myn4Kb H9Nz2T4tDJ8XjCkWfNUfB0Ldim1MFXkOQk6dXZ/eSr+j4A6Y93eih3yk90GTYQVdjv iuDHUZovFOIy6Ef1fwuXyIErv8rcBPcmtTp1c/QGYhJ/Du4//NaPVQpOb5kszMYDTa 9EB6SKKVquFXP23KYaWXkjgaTPpFNqK+KvNWtD2Wam7EAGXOdFs4Xpz1X4riRZs6IE RVOLIFYTvlimg== Date: Fri, 13 Oct 2023 16:43:41 -0700 From: Jakub Kicinski To: Herve Codina Subject: Re: [PATCH v8 24/30] net: wan: Add framer framework support Message-ID: <20231013164341.69c6fd6c@kernel.org> In-Reply-To: <20231011061437.64213-25-herve.codina@bootlin.com> References: <20231011061437.64213-1-herve.codina@bootlin.com> <20231011061437.64213-25-herve.codina@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Andrew Lunn , alsa-devel@alsa-project.org, Thomas Petazzoni , Xiubo Li , Linus Walleij , Jaroslav Kysela , Eric Dumazet , Krzysztof Kozlowski , Fabio Estevam , Qiang Zhao , Shengjiu Wang , Lee Jones , Paolo Abeni , devicetree@vger.kernel.org, Conor Dooley , linux-kernel@vger.kernel.org, Nicolin Chen , linux-gpio@vger.kernel.org, Rob Herring , Christophe JAILLET , Takashi Iwai , linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org, Randy Dunlap , Liam Girdwood , Li Yang , Mark Brown , Simon Horman , lin uxppc-dev@lists.ozlabs.org, "David S. Miller" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed, 11 Oct 2023 08:14:28 +0200 Herve Codina wrote: > A framer is a component in charge of an E1/T1 line interface. > Connected usually to a TDM bus, it converts TDM frames to/from E1/T1 > frames. It also provides information related to the E1/T1 line. > > The framer framework provides a set of APIs for the framer drivers > (framer provider) to create/destroy a framer and APIs for the framer > users (framer consumer) to obtain a reference to the framer, and > use the framer. > > This basic implementation provides a framer abstraction for: > - power on/off the framer > - get the framer status (line state) > - be notified on framer status changes > - get/set the framer configuration Acked-by: Jakub Kicinski