From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<catalin.marinas@arm.com>, <will@kernel.org>
Cc: <arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR by default
Date: Mon, 12 Jun 2023 17:25:44 +0530 [thread overview]
Message-ID: <3362316a-dc24-e2e2-4baa-69e51703e86e@ti.com> (raw)
In-Reply-To: <3ac37e54-0633-37d2-2ba7-f06abcb9a5a7@linaro.org>
On 6/12/23 3:21 PM, Krzysztof Kozlowski wrote:
> On 12/06/2023 11:49, Ravi Gunasekaran wrote:
>>
>>
>> On 6/12/23 3:14 PM, Krzysztof Kozlowski wrote:
>>> On 12/06/2023 11:43, Ravi Gunasekaran wrote:
>>>> Enable HSR feature in kernel build.
>>>
>>> Why? Commit msg should answer to this question.
>>
>> I apologize for incomplete description. I will send out a v2.
>>
>> HSR protocol is implemented by the network stack at /net/hsr/*
>> In order to create HSR interface, HSR module needs to be loaded.
>
> You described what HSR is, but I want to know why do we need it in our
> development arm64 kernel. You might want to enable anything and explain
> what is this "anything" but this does not solve any of the concerns.
>
TI SoCs such as AM64x, AM65x support multiple ethernet ports which can be
used to setup HSR (a redundancy protocol) node in the network. So enabling
the HSR driver to be built as module. The HSR node can be created using a
pair of ethernet ports in the system.
> Best regards,
> Krzysztof
>
--
Regards,
Ravi
prev parent reply other threads:[~2023-06-12 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 9:43 [PATCH] arm64: defconfig: Enable HSR by default Ravi Gunasekaran
2023-06-12 9:44 ` Krzysztof Kozlowski
2023-06-12 9:49 ` [EXTERNAL] " Ravi Gunasekaran
2023-06-12 9:51 ` Krzysztof Kozlowski
2023-06-12 11:55 ` Ravi Gunasekaran [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=3362316a-dc24-e2e2-4baa-69e51703e86e@ti.com \
--to=r-gunasekaran@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
/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