From: Lukasz Majewski <lukma@denx.de>
To: Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Cc: Tristram.Ha@microchip.com,
Oleksij Rempel <o.rempel@pengutronix.de>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [net][hsr] Question regarding HSR RedBox functionality implementation (preferably on KSZ9477)
Date: Tue, 9 Jan 2024 13:32:34 +0100 [thread overview]
Message-ID: <20240109133234.74c47dcd@wsk> (raw)
In-Reply-To: <20231003104410.dhngn3vvdfdcurga@skbuf>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
Dear Community,
I would like to ask you for some help regarding HSR mainline
implementation.
As of now for KSZ9477 we do have working hsr0 (as offloading HW) for
HSR ring operation and some other ports for this IC (like lan3,4,5).
With current setup it is possible to forward packets from HSR ring to
non-HSR network (i.e. plain ethernet) with L3 routing.
However, I'm wondering how the mainline Linux kernel could handle HSR
RedBox functionality (on document [1], Figure 2. we do have "bridge" -
OSI L2).
To be more interesting - br0 can be created between hsr0 and e.g. lan3.
But as expected communication breaks on both directions (to SAN and to
HSR ring).
Is there a similar functionality already present in the Linux kernel
(so this approach could be reused)?
My (very rough idea) would be to extend KSZ9477 bridge join functions
to check if HSR capable interface is "bridged" and then handle frames
in a special way.
However, I would like to first ask for as much input as possible - to
avoid any unnecessary work.
Thanks in advance for help :-)
Link:
[1] -
https://ww1.microchip.com/downloads/en/Appnotes/AN3474-KSZ9477-High-Availability-Seamless-Redundancy-Application-Note-00003474A.pdf
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-09 12:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 13:31 [PATCH v6 net-next 0/5] net: dsa: hsr: Enable HSR HW offloading for KSZ9477 Lukasz Majewski
2023-09-22 13:31 ` [PATCH v6 net-next 1/5] net: dsa: propagate extack to ds->ops->port_hsr_join() Lukasz Majewski
2023-09-26 22:44 ` Vladimir Oltean
2023-09-22 13:31 ` [PATCH v6 net-next 2/5] net: dsa: notify drivers of MAC address changes on user ports Lukasz Majewski
2023-09-22 13:31 ` [PATCH v6 net-next 3/5] net: dsa: tag_ksz: Extend ksz9477_xmit() for HSR frame duplication Lukasz Majewski
2023-09-22 13:31 ` [PATCH v6 net-next 4/5] net: dsa: microchip: move REG_SW_MAC_ADDR to dev->info->regs[] Lukasz Majewski
2023-09-22 13:31 ` [PATCH v6 net-next 5/5] net: dsa: microchip: Enable HSR offloading for KSZ9477 Lukasz Majewski
2023-09-26 22:54 ` [PATCH v6 net-next 0/5] net: dsa: hsr: Enable HSR HW " Vladimir Oltean
2023-09-28 10:41 ` Lukasz Majewski
2023-10-03 7:58 ` Lukasz Majewski
2023-10-03 10:44 ` Vladimir Oltean
2023-10-03 12:51 ` Lukasz Majewski
2023-10-03 13:42 ` Jakub Kicinski
2023-10-03 14:15 ` Lukasz Majewski
2024-01-09 12:32 ` Lukasz Majewski [this message]
2024-01-09 12:52 ` [net][hsr] Question regarding HSR RedBox functionality implementation (preferably on KSZ9477) Vladimir Oltean
2024-01-09 14:04 ` Lukasz Majewski
2024-02-14 10:44 ` Lukasz Majewski
2024-02-15 11:51 ` Lukasz Majewski
2024-02-15 17:23 ` Stephen Hemminger
2023-10-03 13:50 ` [PATCH v6 net-next 0/5] net: dsa: hsr: Enable HSR HW offloading for KSZ9477 patchwork-bot+netdevbpf
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=20240109133234.74c47dcd@wsk \
--to=lukma@denx.de \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.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;
as well as URLs for NNTP newsgroup(s).