From: Greg KH <gregkh@linuxfoundation.org>
To: Ricky Wu <ricky_wu@realtek.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
ulf.hansson@linaro.org, frank.li@vivo.com,
u.kleine-koenig@pengutronix.de, linux-mmc@vger.kernel.org
Subject: Re: [PATCH v6 1/3] misc: rtsx: add to support new card reader rts5264 new definition and function
Date: Thu, 7 Dec 2023 11:14:32 +0900 [thread overview]
Message-ID: <2023120715-reenact-repose-906c@gregkh> (raw)
In-Reply-To: <20231129034856.2001223-2-ricky_wu@realtek.com>
On Wed, Nov 29, 2023 at 11:48:54AM +0800, Ricky Wu wrote:
> in order to support NEW chip rts5264, the definitions of some internal
> registers are define in new file rts5264.h, and some callback functions
> and the workflow for rts5264 are define in new file rts5264.c
>
> also add rts5264.o to Makefile
>
> Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
> ---
> v4: split new definition part up from v3
> ---
> drivers/misc/cardreader/Makefile | 2 +-
> drivers/misc/cardreader/rts5264.c | 886 ++++++++++++++++++++++++++++++
> drivers/misc/cardreader/rts5264.h | 278 ++++++++++
> 3 files changed, 1165 insertions(+), 1 deletion(-)
> create mode 100644 drivers/misc/cardreader/rts5264.c
> create mode 100644 drivers/misc/cardreader/rts5264.h
When building with this change applied, I get lots of build errors. How
did you test this?
My errors are:
CC [M] drivers/misc/cardreader/rts5264.o
drivers/misc/cardreader/rts5264.c: In function ‘rts5264_process_ocp’:
drivers/misc/cardreader/rts5264.c:398:40: error: ‘struct rtsx_pcr’ has no member named ‘ovp_stat’; did you mean ‘ocp_stat’?
398 | rts5264_get_ovpstat(pcr, &pcr->ovp_stat);
| ^~~~~~~~
| ocp_stat
drivers/misc/cardreader/rts5264.c:402:31: error: ‘struct rtsx_pcr’ has no member named ‘ovp_stat’; did you mean ‘ocp_stat’?
402 | (pcr->ovp_stat & (RTS5264_OVP_NOW | RTS5264_OVP_EVER))) {
| ^~~~~~~~
| ocp_stat
drivers/misc/cardreader/rts5264.c:408:22: error: ‘struct rtsx_pcr’ has no member named ‘ovp_stat’; did you mean ‘ocp_stat’?
408 | pcr->ovp_stat = 0;
| ^~~~~~~~
| ocp_stat
drivers/misc/cardreader/rts5264.c: In function ‘rts5264_extra_init_hw’:
drivers/misc/cardreader/rts5264.c:534:38: error: ‘RTS5264_AUTOLOAD_CFG2’ undeclared (first use in this function); did you mean ‘RTS5264_AUTOLOAD_CFG3’?
534 | rtsx_pci_write_register(pcr, RTS5264_AUTOLOAD_CFG2,
| ^~~~~~~~~~~~~~~~~~~~~
| RTS5264_AUTOLOAD_CFG3
drivers/misc/cardreader/rts5264.c:534:38: note: each undeclared identifier is reported only once for each function it appears in
drivers/misc/cardreader/rts5264.c:535:25: error: ‘RTS5264_CHIP_RST_N_SEL’ undeclared (first use in this function); did you mean ‘RTS5264_NON_XTAL_SEL’?
535 | RTS5264_CHIP_RST_N_SEL, 0);
| ^~~~~~~~~~~~~~~~~~~~~~
| RTS5264_NON_XTAL_SEL
drivers/misc/cardreader/rts5264.c:538:38: error: ‘CDGW’ undeclared (first use in this function)
538 | rtsx_pci_write_register(pcr, CDGW, 0xFF, 0x01);
| ^~~~
drivers/misc/cardreader/rts5264.c: In function ‘rts5264_init_params’:
drivers/misc/cardreader/rts5264.c:883:51: error: ‘SD_OVP_INT_EN’ undeclared (first use in this function); did you mean ‘SD_OCP_INT_EN’?
883 | hw_param->interrupt_en |= (SD_OC_INT_EN | SD_OVP_INT_EN);
| ^~~~~~~~~~~~~
| SD_OCP_INT_EN
make[5]: *** [scripts/Makefile.build:243: drivers/misc/cardreader/rts5264.o] Error 1
Remember, each commit can not break the build. Please fix up this series to
build properly at each commit.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-07 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 3:48 [PATCH v6 0/3] Support new card reader rts5264 Ricky Wu
2023-11-29 3:48 ` [PATCH v6 1/3] misc: rtsx: add to support new card reader rts5264 new definition and function Ricky Wu
2023-12-07 2:14 ` Greg KH [this message]
2023-12-08 3:27 ` Ricky WU
2023-11-29 3:48 ` [PATCH v6 2/3] misc: rtsx: add to support new card reader rts5264 Ricky Wu
2023-11-29 3:48 ` [PATCH v6 3/3] mmc: rtsx: add rts5264 to support sd express card Ricky Wu
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=2023120715-reenact-repose-906c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=frank.li@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=ulf.hansson@linaro.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