From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jim Liu <jim.t90615@gmail.com>,
JJLIU0@nuvoton.com, krzysztof.kozlowski+dt@linaro.org,
linus.walleij@linaro.org, andy@kernel.org, robh+dt@kernel.org,
conor+dt@kernel.org, KWLIU@nuvoton.com
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v8 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver
Date: Wed, 6 Dec 2023 13:36:12 +0100 [thread overview]
Message-ID: <701278db-2ea3-49eb-a292-67294d3fdfa5@linaro.org> (raw)
In-Reply-To: <20231206014530.1600151-4-jim.t90615@gmail.com>
On 06/12/2023 02:45, Jim Liu wrote:
> Add Nuvoton BMC NPCM7xx/NPCM8xx sgpio driver support.
> Nuvoton NPCM SGPIO module is combine serial to parallel IC (HC595)
> and parallel to serial IC (HC165), and use APB3 clock to control it.
> This interface has 4 pins (D_out , D_in, S_CLK, LDSH).
> BMC can use this driver to increase 64 GPI pins and 64 GPO pins to use.
>
> Signed-off-by: Jim Liu <jim.t90615@gmail.com>
> ---
...
> + switch (reg) {
> + case READ_DATA:
> + return gpio->base + bank->rdata_reg;
> + case WRITE_DATA:
> + return gpio->base + bank->wdata_reg;
> + case EVENT_CFG:
> + return gpio->base + bank->event_config;
> + case EVENT_STS:
> + return gpio->base + bank->event_status;
> + default:
> + /* actually if code runs to here, it's an error case */
> + dev_WARN(true, "Getting here is an error condition");
So you did not even compile your code. v8 and still not built :(
> + }
> + return 0;
> +}
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-06 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 1:45 [PATCH v8 0/3] Add Nuvoton NPCM SGPIO feature Jim Liu
2023-12-06 1:45 ` [PATCH v8 1/3] dt-bindings: gpio: add NPCM sgpio driver bindings Jim Liu
2023-12-06 1:45 ` [PATCH v8 2/3] arm: dts: nuvoton: npcm: Add sgpio feature Jim Liu
2023-12-06 1:45 ` [PATCH v8 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver Jim Liu
2023-12-06 12:28 ` kernel test robot
2023-12-06 12:36 ` Krzysztof Kozlowski [this message]
2023-12-07 0:16 ` kernel test robot
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=701278db-2ea3-49eb-a292-67294d3fdfa5@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=JJLIU0@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jim.t90615@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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).