From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yanli Yang <yanli.yang@bedmex.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Zhirun Liu <zhirunliu@aicsemi.com>,
Dijia Xu <dijiaxu@aicsemi.com>,
Chunqiu Liu <chunqiuliu@aicsemi.com>,
Liheng Wei <liheng.wei@bedmex.com>
Subject: Re: [RFC PATCH wireless-next v3 3/4] wifi: aic: add FullMAC WLAN driver
Date: Sat, 29 Aug 2026 10:21:00 +0200 [thread overview]
Message-ID: <229f5d99-4aae-4f51-baee-37794c2236dc@kernel.org> (raw)
In-Reply-To: <f22a875eefa398eea9fc80bff1468dfacc47c683.1787903339.git.yanli.yang@bedmex.com>
On 28/08/2026 14:11, Yanli Yang wrote:
> +
> +#ifndef CONFIG_PLATFORM_EXTERNAL
> +#ifdef CONFIG_GPIO_WAKEUP
> +static int wakeup_enable;
> +static u32 hostwake_irq_num;
> +#endif
> +#endif
> +
What?
> +/* debug trace */
> +// static struct wakeup_source *ws_rx_sdio;
> +// static struct wakeup_source *ws_sdio_pwrctrl;
> +// static struct wakeup_source *ws_tx_sdio;
> +#ifdef CONFIG_GPIO_WAKEUP
> +// static struct wakeup_source *ws;
> +#endif
> +
> +#ifdef CONFIG_PLATFORM_EXTERNAL
NAK, there is no such CONFIG symbol.
> +
> +#define ENTER() (pr_info("AICWF enter %s\n", __func__))
> +#define LEAVE() (pr_info("AICWF exit %s\n", __func__))
No. You cannot re-implement tracing. Drop this from EVERYWHERE.
> +
> +int regist_wakeup_irq(struct aic_sdio_dev *sdiodev)
> +{
> + int ret = -EINVAL;
> + struct device *dev = sdiodev->dev;
> + struct device_node *node;
> +
> + ENTER();
> +
> + node = of_find_compatible_node(NULL, NULL, "aic,wifi-wake-host");
Undocumented ABI. Would not be accepted anyway.
> + if (!node)
> + goto err_exit;
>
This driver does not look like upstream code at all. You should clean it
up before you post next v4.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-29 8:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 2:13 [RFC PATCH wireless-next v2 0/4] wifi: aic: add AIC8800 SDIO FullMAC driver Yanli Yang
2026-07-23 2:13 ` [RFC PATCH wireless-next v2 1/4] wifi: aic: add SDIO BSP and build configuration Yanli Yang
2026-07-23 2:13 ` [RFC PATCH wireless-next v2 2/4] wifi: aic: add FullMAC firmware and platform interface Yanli Yang
2026-07-23 2:13 ` [RFC PATCH wireless-next v2 3/4] wifi: aic: add FullMAC WLAN driver Yanli Yang
2026-07-23 2:13 ` [RFC PATCH wireless-next v2 4/4] wifi: aic: integrate AIC8800 driver Yanli Yang
2026-07-23 8:42 ` [RFC PATCH wireless-next v2 0/4] wifi: aic: add AIC8800 SDIO FullMAC driver Johannes Berg
2026-07-23 8:48 ` Johannes Berg
2026-08-28 12:11 ` [RFC PATCH wireless-next v3 0/4] wifi: aic: add AIC8800D80 " Yanli Yang
2026-08-28 12:11 ` [RFC PATCH wireless-next v3 1/4] wifi: aic: add SDIO BSP and build configuration Yanli Yang
2026-08-29 8:18 ` Krzysztof Kozlowski
2026-08-28 12:11 ` [RFC PATCH wireless-next v3 2/4] wifi: aic: add FullMAC firmware and platform interface Yanli Yang
2026-08-28 12:11 ` [RFC PATCH wireless-next v3 3/4] wifi: aic: add FullMAC WLAN driver Yanli Yang
2026-08-29 8:21 ` Krzysztof Kozlowski [this message]
2026-08-28 12:11 ` [RFC PATCH wireless-next v3 4/4] wifi: aic: integrate AIC8800 driver Yanli Yang
2026-08-29 8:21 ` [RFC PATCH wireless-next v4 0/4] wifi: aic: add AIC8800D80 SDIO FullMAC driver Yanli Yang
2026-08-29 8:21 ` [RFC PATCH wireless-next v4 1/4] wifi: aic: add SDIO BSP and build configuration Yanli Yang
2026-08-29 8:21 ` [RFC PATCH wireless-next v4 2/4] wifi: aic: add FullMAC firmware and platform interface Yanli Yang
2026-08-29 8:21 ` [RFC PATCH wireless-next v4 3/4] wifi: aic: add FullMAC WLAN driver Yanli Yang
2026-08-29 8:21 ` [RFC PATCH wireless-next v4 4/4] wifi: aic: integrate AIC8800 driver Yanli Yang
2026-08-31 7:16 ` [RFC PATCH wireless-next v4 0/4] wifi: aic: add AIC8800D80 SDIO FullMAC driver Christian Hewitt
2026-09-06 13:44 ` [RFC PATCH wireless-next v3 " Johannes Berg
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=229f5d99-4aae-4f51-baee-37794c2236dc@kernel.org \
--to=krzk@kernel.org \
--cc=chunqiuliu@aicsemi.com \
--cc=dijiaxu@aicsemi.com \
--cc=johannes@sipsolutions.net \
--cc=liheng.wei@bedmex.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yanli.yang@bedmex.com \
--cc=zhirunliu@aicsemi.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.