From: Kalle Valo <kvalo@kernel.org>
To: Ian Lin <ian.lin@infineon.com>
Cc: <linux-wireless@vger.kernel.org>,
<brcm80211-dev-list@broadcom.com>,
<brcm80211-dev-list@cypress.com>, <franky.lin@broadcom.com>,
<hante.meuleman@broadcom.com>, <Double.Lo@infineon.com>
Subject: Re: [PATCH 1/3] brcmfmac: add a timer to read console periodically in PCIE bus
Date: Tue, 04 Oct 2022 10:07:26 +0300 [thread overview]
Message-ID: <87edvoqd75.fsf@kernel.org> (raw)
In-Reply-To: <20220929031001.9962-2-ian.lin@infineon.com> (Ian Lin's message of "Wed, 28 Sep 2022 22:09:59 -0500")
Ian Lin <ian.lin@infineon.com> writes:
> From: Wright Feng <wright.feng@cypress.com>
>
> Currently, host only reads console buffer when receiving mailbox data or
> hit crash with PCIE bus. Therefore, we add timer in PCIE code to read
> console buffer periodically to help developer and user check firmware
> message when there is no data transmission between host and dongle.
>
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
> Signed-off-by: Chi-hsien Lin <chi-hsien.lin@cypress.com>
> Signed-off-by: Ian Lin <ian.lin@infineon.com>
[...]
> @@ -340,6 +342,11 @@ struct brcmf_pciedev_info {
> u16 value);
> struct brcmf_mp_device *settings;
> struct brcmf_otp_params otp;
> +#ifdef DEBUG
> + u32 console_interval;
> + bool console_active;
> + struct timer_list timer;
> +#endif
> };
I was wondering where that DEBUG is defined and found that it's done in
the Makefile:
subdir-ccflags-$(CONFIG_BRCMDBG) += -DDEBUG
I think that DEBUG define should be removed and instead CONFIG_BRCMDBG
should be used all over the brcmfmac and brcmsmac code. A cleanup patch
doing this is very welcome.
This would be a good task for someone new to kernel development, is
there a way to report these kind of simple tasks?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-10-04 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 3:09 [PATCH 0/3] brcmfmac: PCIE debug mechanism series Ian Lin
2022-09-29 3:09 ` [PATCH 1/3] brcmfmac: add a timer to read console periodically in PCIE bus Ian Lin
2022-10-04 7:07 ` Kalle Valo [this message]
2022-10-04 8:28 ` Kalle Valo
2022-10-10 9:53 ` Arend Van Spriel
2022-09-29 3:10 ` [PATCH 2/3] brcmfmac: return error when getting invalid max_flowrings from dongle Ian Lin
2022-10-10 9:58 ` Arend Van Spriel
2023-01-08 20:53 ` chainofflowers
2023-01-09 8:52 ` Arend van Spriel
2023-01-09 17:23 ` chainofflowers
2022-09-29 3:10 ` [PATCH 3/3] brcmfmac: dump dongle memory when attaching failed Ian Lin
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=87edvoqd75.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Double.Lo@infineon.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian.lin@infineon.com \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).