From: Greg KH <gregkh@linuxfoundation.org>
To: Manjae Cho <manjae.cho@samsung.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Improve MAR register definition and usage for rtl8723
Date: Wed, 31 Jul 2024 08:16:58 +0200 [thread overview]
Message-ID: <2024073109-abridge-yapping-3db3@gregkh> (raw)
In-Reply-To: <20240730155054.411059-1-manjae.cho@samsung.com>
On Wed, Jul 31, 2024 at 12:50:54AM +0900, Manjae Cho wrote:
> This patch improves the usage of the MAR register by updating the
> relevant
> macro definitions and ensuring consistent usage across the codebase.
>
> Signed-off-by: Manjae Cho <manjae.cho@samsung.com>
>
> ---
> drivers/staging/rtl8723bs/hal/sdio_halinit.c | 4 ++--
> drivers/staging/rtl8723bs/include/hal_com_reg.h | 3 +++
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/sdio_halinit.c b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> index c9cd6578f7f8..9493562c1619 100644
> --- a/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> +++ b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> @@ -380,8 +380,8 @@ static void _InitWMACSetting(struct adapter *padapter)
> rtw_write32(padapter, REG_RCR, pHalData->ReceiveConfig);
>
> /* Accept all multicast address */
> - rtw_write32(padapter, REG_MAR, 0xFFFFFFFF);
> - rtw_write32(padapter, REG_MAR + 4, 0xFFFFFFFF);
> + rtw_write32(padapter, MAR0, 0xFFFFFFFF);
> + rtw_write32(padapter, MAR4, 0xFFFFFFFF);
>
> /* Accept all data frames */
> value16 = 0xFFFF;
> diff --git a/drivers/staging/rtl8723bs/include/hal_com_reg.h b/drivers/staging/rtl8723bs/include/hal_com_reg.h
> index 9a02ae69d7a4..baf326d53a46 100644
> --- a/drivers/staging/rtl8723bs/include/hal_com_reg.h
> +++ b/drivers/staging/rtl8723bs/include/hal_com_reg.h
> @@ -151,6 +151,9 @@
> #define REG_BSSID 0x0618
> #define REG_MAR 0x0620
>
> +#define MAR0 REG_MAR /* Multicast Address Register, Offset 0x0620-0x0623 */
Why redefine this value again? What is wrong with using it as
"REG_MAR"? Is this fixing anything or making anything more consistent
somewhere? It's only used in one place that I can see.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-31 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240730155255epcas1p4ab3b5e88d400e2221aa1cf5cf234ea19@epcas1p4.samsung.com>
2024-07-30 15:50 ` [PATCH] Improve MAR register definition and usage for rtl8723 Manjae Cho
2024-07-30 18:55 ` Philipp Hortmann
2024-07-31 5:28 ` Greg KH
2024-07-31 6:16 ` Greg KH [this message]
2024-07-31 6:55 ` Manjae Cho
2024-07-31 7:26 ` 'Greg KH'
2024-07-31 8:01 ` Manjae Cho
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=2024073109-abridge-yapping-3db3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manjae.cho@samsung.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