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 shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (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 43227C001DF for ; Thu, 3 Aug 2023 15:26:47 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96) (envelope-from ) id 1qRaD3-00060f-18; Thu, 03 Aug 2023 11:25:53 -0400 Received: from mail-pf1-x42b.google.com ([2607:f8b0:4864:20::42b]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qRaD0-00060X-2K for kernelnewbies@kernelnewbies.org; Thu, 03 Aug 2023 11:25:50 -0400 Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-686bea20652so983197b3a.1 for ; Thu, 03 Aug 2023 08:25:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691076343; x=1691681143; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=iP3kTEqKJC/oDuTXJHTWiz/U+/XJV4DMI2sNhnRpi7E=; b=I0DoKX+zGa8uvARRmfC4HwErwybReWEprLe57cB4GyO8aolQDpp8qncEoeAW3oJO33 9WTQu1DVa+WnSbwb0o1JUIPTxPtcvtYt5hPJ8HypULT2waV2kO/Du7oHsAC272fikOrf eWub3+uvY6rANX+4peR2VIIzAHAC02B6I7ef/PU3ATnOt9sGzAM/xDAV/C6k26nLYHzV MuXiLdbr+Z+M7V5EBZqgojll/gXc73sj8Y3ReNlzNcIhWHPCuOZWvCSzPxqgI7feLCa7 Mulk+xlhMVRFhW5xrdapDTkkNyYt3K8T2FSTiMDluRa4ODglO5Xv6DALtRCuey66g6xC CN7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691076343; x=1691681143; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iP3kTEqKJC/oDuTXJHTWiz/U+/XJV4DMI2sNhnRpi7E=; b=ZUU2MdCOvuCl5knB7LPeiIP9CUKhhHMEHCB4Y9hKLKmSSPFNbCBiFMvRVksn+uVQK6 zVjL7iuSdxhc5Rkf+9FR2Vn6F5j8M/n9hS0VxOovW86r7tu5ei9xmw/IxynkWl9AqZTn VKHWOahXnqOHQJvPNC+I/2IlYEU61mMrY6LtQsAlf9yTkwInEjATnlEaqMaCeLV2mFgu ppFeokwtEk7cpJxgPqPGHHq4GEgiU4P6G+zrBASMpA+1G/W4icjUh4Mu75G4mTs1y0np QRTeXHHjMrJx0bmOQFTywu+9VSUEITIE/2TYdSuJzFpF8dw6fkD45+n1rj8tQ2g3Ldio Ne5A== X-Gm-Message-State: ABy/qLbPlJQMR79XLrZxwztDSC/UMWr2feum7zB6j2EhFq3smY711DSS a7xRtu/rFT9uw60/zGTOdU/LZ/h0XPDXWkqq X-Google-Smtp-Source: APBJJlES5AEify9YCQ+NweLyPqmrcClsGX/bYvD/nQzyt2zsOU1AeMg2TcIuc9c1IbGmdvmPhniHCg== X-Received: by 2002:a05:6a20:430d:b0:126:af02:444e with SMTP id h13-20020a056a20430d00b00126af02444emr25022833pzk.8.1691076343195; Thu, 03 Aug 2023 08:25:43 -0700 (PDT) Received: from [172.16.116.58] ([103.15.228.66]) by smtp.gmail.com with ESMTPSA id e8-20020aa78248000000b00686dd062207sm905pfn.150.2023.08.03.08.25.41 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Aug 2023 08:25:42 -0700 (PDT) Message-ID: <776435cc-1314-22c7-4ff9-88078496b11a@gmail.com> Date: Thu, 3 Aug 2023 20:54:06 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Content-Language: en-US To: kernelnewbies@kernelnewbies.org From: Ayush Singh Subject: Using net/wan/hdlc with serdev X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4556060005157710679==" Errors-To: kernelnewbies-bounces@kernelnewbies.org This is a multi-part message in MIME format. --===============4556060005157710679== Content-Type: multipart/alternative; boundary="------------o1BbwEKlM61MO93vHhHzQ0sm" Content-Language: en-US This is a multi-part message in MIME format. --------------o1BbwEKlM61MO93vHhHzQ0sm Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello everyone. I have a serdev driver that communicates with a coprocessor using HDLC [1]. I am currently using my own HDLC implementation, but someone pointed out to me that I might be able to use `drivers/net/wan/hdlc` instead. However, I am not quite sure how I am supposed to use it. I think I am supposed to `register_hdlc_protocol` in the serdev probe. The `hdlc_proto->netif_rx` callback is called when data is available, and `hdlc_proto->xmit` is called to send data? What is the format of `skb-data` in rx? It would be great if someone could point me to some drivers that use Linux internal HDLC implementation. Ayush Singh [1]: https://git.beagleboard.org/gsoc/greybus/beagleplay-greybus-driver/-/tree/develop --------------o1BbwEKlM61MO93vHhHzQ0sm Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hello everyone. I have a serdev driver that communicates with a coprocessor using HDLC [1]. I am currently using my own HDLC implementation, but someone pointed out to me that I might be able to use `drivers/net/wan/hdlc` instead.

However, I am not quite sure how I am supposed to use it. I think I am supposed to `register_hdlc_protocol` in the serdev probe. The `hdlc_proto->netif_rx` callback is called when data is available, and `hdlc_proto->xmit` is called to send data? What is the format of `skb-data` in rx?

It would be great if someone could point me to some drivers that use Linux internal HDLC implementation.


Ayush Singh


[1]: https://git.beagleboard.org/gsoc/greybus/beagleplay-greybus-driver/-/tree/develop

--------------o1BbwEKlM61MO93vHhHzQ0sm-- --===============4556060005157710679== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============4556060005157710679==--