From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Leo Li <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Heiko Thiery <heiko.thiery@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] Revert "arm64: dts: ls1028a: sl28: use ocelot-8021q tagging by default"
Date: Thu, 27 Oct 2022 18:00:04 +0200 [thread overview]
Message-ID: <84c5e0a041909615a1ba8a4508131206@walle.cc> (raw)
In-Reply-To: <20221027122727.fhs35eqtzmeen6x4@skbuf>
Am 2022-10-27 14:27, schrieb Vladimir Oltean:
>> Pretty nasty. Of all the switch drivers that support tagging protocol
>> change, Ocelot/Felix is the only one with this bug, because in all
>> other
>> cases, the default and the alternative tagging protocol are part of
>> the
>> same .ko. Only here we have tag_ocelot.ko and tag_ocelot_8021q.ko.
>>
>> The problem preventing us from calling request_module() is that
>> currently,
>> the string identifying the tagging protocol (to which we match device
>> tree information) is part of the tag_*.ko. I think we'd need the
>> translation table between string and enum dsa_tag_protocol to be part
>> of
>> dsa_core.ko.
>
> I think we should treat what we committed to in terms of dt-bindings
> with utmost respect, so I would consider your proposed revert as the
> absolute last option. Reverting a device tree change doesn't mean that
> the device trees without the revert will disappear from circulation.
>
> So far we have 3 options for fixing this within the kernel
>
> - make tag_ocelot.o and tag_ocelot_8021q.o link into the same
> tag_ocelot.ko
>
> - change the MODULE_ALIAS() of all tagging protocol driver modules from
> "dsa_tag-<number" to something containing their string name - what
> you
> proposed. I don't know why the current MODULE_ALIAS() is formatted
> the
> way it is. Maybe Andrew can comment on whether this is feasible.
> I think there isn't any backwards compatibility concern, since only
> modules compiled for a certain kernel version are expected to be
> loaded.
FWIW, you can have multiple aliases if we somehow need to keep the IDs,
too.
> - put a translation table between string and MODULE_ALIAS() inside
> dsa_core.ko, which potentially duplicates code. Maybe if we
> auto-generate it somehow?
Yeah, I also thought of a table with of name to module alias mapping.
But then you'd have two places to keep in sync (of not autogenerated).
-michael
next prev parent reply other threads:[~2022-10-27 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 11:32 [PATCH] Revert "arm64: dts: ls1028a: sl28: use ocelot-8021q tagging by default" Michael Walle
2022-10-27 12:05 ` Vladimir Oltean
2022-10-27 12:27 ` Vladimir Oltean
2022-10-27 12:40 ` Vladimir Oltean
2022-10-27 13:00 ` Michael Walle
2022-10-27 13:54 ` Vladimir Oltean
2022-10-27 16:00 ` Michael Walle [this message]
2022-10-27 18:04 ` Vladimir Oltean
2022-10-27 19:10 ` Michael Walle
2022-10-27 20:36 ` Vladimir Oltean
2022-10-27 16:14 ` Michael Walle
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=84c5e0a041909615a1ba8a4508131206@walle.cc \
--to=michael@walle.cc \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir.oltean@nxp.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).