From: Simon Horman <horms@kernel.org>
To: Michael Nemanov <michael.nemanov@ti.com>
Cc: Kalle Valo <kvalo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sabeeh Khan <sabeeh-khan@ti.com>
Subject: Re: [PATCH v4 09/17] wifi: cc33xx: Add main.c
Date: Sat, 2 Nov 2024 13:25:32 +0000 [thread overview]
Message-ID: <20241102132532.GJ1838431@kernel.org> (raw)
In-Reply-To: <20241029172354.4027886-10-michael.nemanov@ti.com>
On Tue, Oct 29, 2024 at 07:23:46PM +0200, Michael Nemanov wrote:
> General code and structures.
> Notably:
>
> cc33xx_irq - Handles IRQs received from the device.
>
> process_core_status - Core status is a new concept in CC33xx.
> it's a structure that is appended to each transfer from the device and
> contains its most up-to-date status report (IRQs, buffers, etc.).
> See struct core_status for details.
>
> process_event_and_cmd_result - Responses to driver commands and
> FW events both arrive asynchronously. Therefore, driver cannot know what
> he read from HW until inspecting the payload. This code reads and
> dispatches the data accordingly.
>
> cc33xx_recovery_work - Driver supports basic recovery on FW crash and
> other illegal conditions. This implements the recovery flow
> (Remove all vifs, turn device off and on, download FW,
> let ieee80211_restart_hw do the rest).
>
> irq_deferred_work - Does irq-related work that requires holding the
> cc->mutex. Thisd is mostly in response to HW's Tx/Rx IRQs.
>
> cc33xx_nvs_cb - Callback for the NVS FW request API. Similar to wlcore,
> this is where the init of the HW is performed.
>
> cc33xx_load_ini_bin_file - Loads a configuration file from user-space
> via the request FW API. The structure is described in a separate patch.
>
> cc33xx_op_X - MAC80211 operation handlers.
>
> Signed-off-by: Michael Nemanov <michael.nemanov@ti.com>
> ---
> drivers/net/wireless/ti/cc33xx/main.c | 5689 +++++++++++++++++++++++++
> 1 file changed, 5689 insertions(+)
> create mode 100644 drivers/net/wireless/ti/cc33xx/main.c
>
> diff --git a/drivers/net/wireless/ti/cc33xx/main.c b/drivers/net/wireless/ti/cc33xx/main.c
...
> +static struct ieee80211_sband_iftype_data iftype_data_2ghz[] = {{
Hi Michael,
Sparse seems a bit unhappy about this:
.../main.c:332:24: warning: incorrect type in initializer (different address spaces)
.../main.c:332:24: expected struct ieee80211_sband_iftype_data const [noderef] __iftype_data *iftype_data
.../main.c:332:24: got struct ieee80211_sband_iftype_data *
So perhaps it should be:
static const struct ieee80211_sband_iftype_data __iftd iftype_data_2ghz[] = {{
Likewise for iftype_data_5ghz.
...
next prev parent reply other threads:[~2024-11-02 13:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 17:23 [PATCH v4 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 01/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml Michael Nemanov
2024-10-29 17:28 ` Krzysztof Kozlowski
2024-10-30 10:59 ` Nemanov, Michael
2024-10-30 11:09 ` Krzysztof Kozlowski
2024-10-30 12:14 ` Nemanov, Michael
2024-10-30 14:01 ` Krzysztof Kozlowski
2024-10-29 17:23 ` [PATCH v4 02/17] wifi: cc33xx: Add cc33xx.h, cc33xx_i.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 03/17] wifi: cc33xx: Add debug.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 04/17] wifi: cc33xx: Add sdio.c, io.c, io.h Michael Nemanov
2024-10-29 17:34 ` Krzysztof Kozlowski
2024-11-03 13:33 ` Nemanov, Michael
2024-10-29 17:23 ` [PATCH v4 05/17] wifi: cc33xx: Add cmd.c, cmd.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 06/17] wifi: cc33xx: Add acx.c, acx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 07/17] wifi: cc33xx: Add event.c, event.h Michael Nemanov
2024-11-02 13:12 ` Simon Horman
2024-10-29 17:23 ` [PATCH v4 08/17] wifi: cc33xx: Add boot.c, boot.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 09/17] wifi: cc33xx: Add main.c Michael Nemanov
2024-11-02 13:25 ` Simon Horman [this message]
2024-11-03 12:55 ` Nemanov, Michael
2024-10-29 17:23 ` [PATCH v4 10/17] wifi: cc33xx: Add rx.c, rx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 11/17] wifi: cc33xx: Add tx.c, tx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 12/17] wifi: cc33xx: Add init.c, init.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 13/17] wifi: cc33xx: Add scan.c, scan.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 14/17] wifi: cc33xx: Add conf.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 15/17] wifi: cc33xx: Add ps.c, ps.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 16/17] wifi: cc33xx: Add testmode.c, testmode.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 17/17] wifi: cc33xx: Add Kconfig, Makefile Michael Nemanov
2024-10-29 17:55 ` Krzysztof Kozlowski
2024-10-30 14:11 ` kernel test robot
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=20241102132532.GJ1838431@kernel.org \
--to=horms@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael.nemanov@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sabeeh-khan@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.