From: "TY_Chang[張子逸]" <tychang@realtek.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"kernel test robot" <lkp@intel.com>
Subject: RE: [linusw-pinctrl:devel] BUILD SUCCESS WITH WARNING e8b4ff6a856d02ee64a6023edf45e11827badeef
Date: Wed, 18 Oct 2023 03:18:13 +0000 [thread overview]
Message-ID: <97c8604460d34011b87eeb6b302a6b49@realtek.com> (raw)
In-Reply-To: <CACRpkda4SYP5twcxDGA_k4VzV0mh1Q190SZT0u7xqZykrPt=VA@mail.gmail.com>
Hi Linus,
Sorry for the delayed response. I was out of the office in the past few weeks.
>
>Tzuyi, can you look at this, I understand some of the warnings but not all, and I need
>HW knowledge to fix the compile warnings:
>
>On Fri, Sep 29, 2023 at 10:04 AM kernel test robot <lkp@intel.com> wrote:
>
>
>> drivers/pinctrl/realtek/pinctrl-rtd.c:180:29: warning: '%s' directive
>> argument is null [-Wformat-overflow=]
>
>I don't understand this at all.
>
>> drivers/pinctrl/realtek/pinctrl-rtd1315e.c:231:35: warning:
>> 'rtd1315e_boot_sel_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1315e.c:231:35: warning:
>> 'rtd1315e_reset_n_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1315e.c:231:35: warning:
>> 'rtd1315e_scan_switch_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1315e.c:231:35: warning:
>> 'rtd1315e_testmode_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1315e.c:231:35: warning:
>> 'rtd1315e_wd_rset_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1319d.c:237:35: warning:
>> 'rtd1319d_boot_sel_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1319d.c:237:35: warning:
>> 'rtd1319d_reset_n_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1319d.c:237:35: warning:
>> 'rtd1319d_scan_switch_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1319d.c:237:35: warning:
>> 'rtd1319d_testmode_pins' defined but not used
>> [-Wunused-const-variable=]
>> drivers/pinctrl/realtek/pinctrl-rtd1319d.c:237:35: warning:
>> 'rtd1319d_wd_rset_pins' defined but not used
>> [-Wunused-const-variable=]
>
>These appear because there are for example:
>DECLARE_RTD1315E_PIN(RTD1315E_ISO_BOOT_SEL, boot_sel); But no
>corresponding RTD1315E_GROUP().
>
>Can you make a patch adding the missing groups?
>
Those pins are the actual hardware pins on the chips, but they are not currently in use. I forgot to add the groups for them. I'm sorry about that.
I think the patch you've applied in the following link is also a solution. Thank you.
https://patchwork.ozlabs.org/project/linux-gpio/patch/20231006-fix-realtek-warnings-v1-1-09af253312ba@linaro.org/
Thanks,
Tzuyi Chang
next prev parent reply other threads:[~2023-10-18 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 7:13 [linusw-pinctrl:devel] BUILD SUCCESS WITH WARNING e8b4ff6a856d02ee64a6023edf45e11827badeef kernel test robot
2023-09-29 12:06 ` Linus Walleij
2023-10-18 3:18 ` TY_Chang[張子逸] [this message]
2023-10-18 7:25 ` Linus Walleij
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=97c8604460d34011b87eeb6b302a6b49@realtek.com \
--to=tychang@realtek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).