From: Yojana Mallik <y-mallik@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <schnelle@linux.ibm.com>, <wsa+renesas@sang-engineering.com>,
<diogo.ivo@siemens.com>, <rdunlap@infradead.org>,
<horms@kernel.org>, <vigneshr@ti.com>, <rogerq@ti.com>,
<danishanwar@ti.com>, <pabeni@redhat.com>, <kuba@kernel.org>,
<edumazet@google.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<srk@ti.com>, <rogerq@kernel.org>, <y-mallik@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH net-next v2 0/3] Introducing Intercore Virtual Ethernet (ICVE) driver
Date: Wed, 12 Jun 2024 18:18:49 +0530 [thread overview]
Message-ID: <02df751a-dd04-4aa5-8c0f-7f8c98d7e01c@ti.com> (raw)
In-Reply-To: <8f5d2448-bfd7-48a5-be12-fb16cdc4de79@lunn.ch>
On 6/2/24 21:15, Andrew Lunn wrote:
> On Fri, May 31, 2024 at 12:10:03PM +0530, Yojana Mallik wrote:
>> virtio-net provides a solution for virtual ethernet interface in a
>> virtualized environment.
>>
>> There might be a use-case for traffic tunneling between heterogeneous
>> processors in a non virtualized environment such as TI's AM64x that has
>> Cortex A53 and Cortex R5 where Linux runs on A53 and a flavour of RTOS
>> on R5(FreeRTOS) and the ethernet controller is managed by R5 and needs
>> to pass some low priority data to A53.
>>
>> One solution for such an use case where the ethernet controller does
>> not support DMA for Tx/Rx channel, could be a RPMsg based shared memory
>> ethernet driver.
>
> virtio-net is very generic and vendor agnostic.
>
> Looking at icve, what is TI specific? Why not define a generic
> solution which could be used for any heterogeneous system? We are
> seeming more and more such systems, and there is no point everybody
> re-inventing the wheel. So what i would like to see is something
> similar to driver/tty/rpmsg_tty.c, a driver/net/ethernet/rpmsg_eth.c,
> with good documentation of the protocol used, so that others can
> implement it. And since you say you have FreeRTOS on the other end,
> you could also contribute that side to FreeRTOS as well. A complete
> open source solution everybody can use.
>
> Andrew
+static struct rpmsg_device_id icve_rpmsg_id_table[] = {
+ { .name = "ti.icve" },
+ {},
+};
+MODULE_DEVICE_TABLE(rpmsg, icve_rpmsg_id_table);
+
+static struct rpmsg_driver icve_rpmsg_client = {
+ .drv.name = KBUILD_MODNAME,
+ .id_table = icve_rpmsg_id_table,
+ .probe = icve_rpmsg_probe,
+ .callback = icve_rpmsg_cb,
+ .remove = icve_rpmsg_remove,
+};
+module_rpmsg_driver(icve_rpmsg_client);
+
When the Linux kernel detects an rpmsg device (the communication channel), it
looks for a matching driver that can handle this device with the help of name
string in the icve_rpmsg_id_table in driver structure. I will change the name
string to make the driver generic. Apart from the name string other entities
don't look TI specific.
Thank you for the suggestion to make inter-core virtual ethernet driver generic
like drivers/tty/rpmsg_tty.c for a complete open source solution. I will be
working on it.
Regard,
Yojana Mallik
prev parent reply other threads:[~2024-06-12 12:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 6:40 Yojana Mallik
2024-05-31 6:40 ` [PATCH net-next v2 1/3] net: ethernet: ti: RPMsg based shared memory ethernet driver Yojana Mallik
2024-05-31 15:30 ` Randy Dunlap
2024-06-03 5:50 ` Yojana Mallik
2024-06-02 7:01 ` Siddharth Vadapalli
2024-06-03 6:16 ` Yojana Mallik
2024-06-02 16:21 ` Andrew Lunn
2024-06-03 8:56 ` Yojana Mallik
2024-06-03 12:54 ` Andrew Lunn
2024-05-31 6:40 ` [PATCH net-next v2 2/3] net: ethernet: ti: Register the RPMsg driver as network device Yojana Mallik
2024-06-01 3:13 ` kernel test robot
2024-06-03 9:26 ` Yojana Mallik
2024-06-02 7:22 ` Siddharth Vadapalli
2024-06-02 15:54 ` Andrew Lunn
2024-06-02 7:35 ` Siddharth Vadapalli
2024-06-02 16:45 ` Andrew Lunn
2024-06-04 6:23 ` Yojana Mallik
2024-06-04 12:54 ` Andrew Lunn
2024-06-12 12:52 ` Yojana Mallik
2024-06-12 14:59 ` Andrew Lunn
2024-06-14 9:08 ` Yojana Mallik
2024-06-16 16:19 ` Andrew Lunn
2024-06-16 19:03 ` Andrew Lunn
2024-06-04 13:00 ` Andrew Lunn
2024-06-12 12:49 ` Yojana Mallik
2024-06-12 14:36 ` Andrew Lunn
2024-05-31 6:40 ` [PATCH net-next v2 3/3] net: ethernet: ti: icve: Add support for multicast filtering Yojana Mallik
2024-06-03 21:27 ` kernel test robot
2024-06-02 15:45 ` [PATCH net-next v2 0/3] Introducing Intercore Virtual Ethernet (ICVE) driver Andrew Lunn
2024-06-03 23:54 ` Jakub Kicinski
2024-06-12 12:48 ` Yojana Mallik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02df751a-dd04-4aa5-8c0f-7f8c98d7e01c@ti.com \
--to=y-mallik@ti.com \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rogerq@kernel.org \
--cc=rogerq@ti.com \
--cc=s-vadapalli@ti.com \
--cc=schnelle@linux.ibm.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®