From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCHv3 wireless-next 3/7] wifi: rt2800soc: allow loading from OF
Date: Sat, 12 Jul 2025 12:14:18 +0200 [thread overview]
Message-ID: <20250712101418.GD9845@wp.pl> (raw)
In-Reply-To: <20250710200820.262295-4-rosenp@gmail.com>
On Thu, Jul 10, 2025 at 01:08:16PM -0700, Rosen Penev wrote:
> Add a single binding to help the already present dts files load the
> driver. More are possible but there doesn't seem to be a significant
> difference between them to justify this.
>
> Use wifi name per dtschema requirements.
>
> The data field will be used to remove the custom non static probe
> function and use of_device_get_match_data.
>
> Added OF dependency to SOC CONFIG as adding of_match_table without OF
> being present makes no sense.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> Reviewed-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> drivers/net/wireless/ralink/rt2x00/Kconfig | 2 +-
> drivers/net/wireless/ralink/rt2x00/rt2800soc.c | 7 +++++++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/ralink/rt2x00/Kconfig b/drivers/net/wireless/ralink/rt2x00/Kconfig
> index 3a32ceead54f..a0dc9a751234 100644
> --- a/drivers/net/wireless/ralink/rt2x00/Kconfig
> +++ b/drivers/net/wireless/ralink/rt2x00/Kconfig
> @@ -202,7 +202,7 @@ endif
>
> config RT2800SOC
> tristate "Ralink WiSoC support"
> - depends on SOC_RT288X || SOC_RT305X || SOC_MT7620 || COMPILE_TEST
> + depends on OF && (SOC_RT288X || SOC_RT305X || SOC_MT7620 || COMPILE_TEST)
> select RT2X00_LIB_SOC
> select RT2X00_LIB_MMIO
> select RT2X00_LIB_CRYPTO
> diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800soc.c b/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> index e73394cf6ea6..db8d01f0cdc3 100644
> --- a/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> +++ b/drivers/net/wireless/ralink/rt2x00/rt2800soc.c
> @@ -243,9 +243,16 @@ static int rt2800soc_probe(struct platform_device *pdev)
> return rt2x00soc_probe(pdev, &rt2800soc_ops);
> }
>
> +static const struct of_device_id rt2880_wmac_match[] = {
> + { .compatible = "ralink,rt2880-wifi", .data = &rt2800soc_ops },
Why do .data = rt2800soc_ops here and use it via of_device_get_match_data()
in patch 5, insead of just use rt2800soc_ops directly in rt2800soc_probe ?
Regards
Stanislaw
> + {},
> +};
> +MODULE_DEVICE_TABLE(of, rt2880_wmac_match);
> +
> static struct platform_driver rt2800soc_driver = {
> .driver = {
> .name = "rt2800_wmac",
> + .of_match_table = rt2880_wmac_match,
> },
> .probe = rt2800soc_probe,
> .remove = rt2x00soc_remove,
> --
> 2.50.0
>
next prev parent reply other threads:[~2025-07-12 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 20:08 [PATCHv3 wireless-next 0/7] wifi: rt2x00: add OF bindings + cleanup Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 1/7] wifi: rt2x00: add COMPILE_TEST Rosen Penev
2025-07-12 8:59 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 2/7] wifi: rt2x00: remove mod_name from platform_driver Rosen Penev
2025-07-12 8:59 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 3/7] wifi: rt2800soc: allow loading from OF Rosen Penev
2025-07-12 10:14 ` Stanislaw Gruszka [this message]
2025-07-12 19:02 ` Rosen Penev
2025-07-13 7:15 ` Stanislaw Gruszka
2025-07-13 8:49 ` Johannes Berg
2025-07-13 11:06 ` Johannes Berg
2025-07-10 20:08 ` [PATCHv3 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc Rosen Penev
2025-07-12 10:20 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 5/7] wifi: rt2x00: soc: modernize probe Rosen Penev
2025-07-11 14:01 ` Alexander Savchenko
2025-07-11 20:33 ` Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 6/7] MIPS: dts: ralink: mt7620a: add wifi Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 7/7] dt-bindings: net: wireless: rt2800: add Rosen Penev
2025-07-10 21:39 ` Krzysztof Kozlowski
2025-07-10 22:40 ` Rosen Penev
2025-07-11 7:48 ` Krzysztof Kozlowski
2025-07-12 10:40 ` Stanislaw Gruszka
2025-07-12 16:53 ` Krzysztof Kozlowski
2025-07-12 16:59 ` Krzysztof Kozlowski
2025-07-12 23:20 ` Julian Calaby
2025-07-13 8:53 ` Krzysztof Kozlowski
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=20250712101418.GD9845@wp.pl \
--to=stf_xl@wp.pl \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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).