From: Frank Li <Frank.Li@nxp.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Joy Zou <joy.zou@nxp.com>, Dong Aisheng <aisheng.dong@nxp.com>,
Robin Gong <yibin.gong@nxp.com>,
linux-input@vger.kernel.org (open list:INPUT (KEYBOARD, MOUSE,
JOYSTICK, TOUCHSCREEN)...),
linux-kernel@vger.kernel.org (open list)
Cc: imx@lists.linux.dev
Subject: [PATCH 1/2] input: keyboard: snvs_pwrkey: Enable clock when accessing HP* registers
Date: Tue, 16 Jul 2024 16:56:09 -0400 [thread overview]
Message-ID: <20240716205612.1502608-1-Frank.Li@nxp.com> (raw)
From: Robin Gong <yibin.gong@nxp.com>
SNVS requires two clock sources:
- LP (32k always on): All LP* registers need this clock. No management is
needed as it is always on.
- HP: All HP* registers require this clock to be enabled before accessing
these registers. Some platforms (e.g., i.MX6SX/i.MX6UL) do not have a
separate HP root clock and it is always on.
Add an optional "snvs-pwrkey" clock for the HP clock and enable it only
when accessing HP* registers.
Signed-off-by: Robin Gong <yibin.gong@nxp.com>
Signed-off-by: Joy Zou <joy.zou@nxp.com>
Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
- clock name snvs-pwrkey already documented at
Documentation/devicetree/bindings/crypto/fsl,sec-v4.0-mon.yaml
---
drivers/input/keyboard/snvs_pwrkey.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/input/keyboard/snvs_pwrkey.c b/drivers/input/keyboard/snvs_pwrkey.c
index ad8660be0127c..b352148a0cfb2 100644
--- a/drivers/input/keyboard/snvs_pwrkey.c
+++ b/drivers/input/keyboard/snvs_pwrkey.c
@@ -37,6 +37,7 @@ struct pwrkey_drv_data {
int keycode;
int keystate; /* 1:pressed */
int wakeup;
+ struct clk *clk;
struct timer_list check_timer;
struct input_dev *input;
u8 minor_rev;
@@ -48,7 +49,10 @@ static void imx_imx_snvs_check_for_events(struct timer_list *t)
struct input_dev *input = pdata->input;
u32 state;
+ clk_prepare_enable(pdata->clk);
regmap_read(pdata->snvs, SNVS_HPSR_REG, &state);
+ clk_disable_unprepare(pdata->clk);
+
state = state & SNVS_HPSR_BTN ? 1 : 0;
/* only report new event if status changed */
@@ -169,7 +173,15 @@ static int imx_snvs_pwrkey_probe(struct platform_device *pdev)
if (pdata->irq < 0)
return -EINVAL;
+ pdata->clk = devm_clk_get_optional(&pdev->dev, "snvs-pwrkey");
+ if (IS_ERR(pdata->clk))
+ return dev_err_probe(&pdev->dev, PTR_ERR(pdata->clk),
+ "Could not get the snvs-pwrkey clock");
+
+ clk_prepare_enable(pdata->clk);
regmap_read(pdata->snvs, SNVS_HPVIDR1_REG, &vid);
+ clk_disable_unprepare(pdata->clk);
+
pdata->minor_rev = vid & 0xff;
regmap_update_bits(pdata->snvs, SNVS_LPCR_REG, SNVS_LPCR_DEP_EN, SNVS_LPCR_DEP_EN);
--
2.34.1
next reply other threads:[~2024-07-16 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 20:56 Frank Li [this message]
2024-07-16 20:56 ` [PATCH 2/2] input: keyboard: snvs_pwrkey: Fix missed key press after suspend Frank Li
2024-07-16 20:56 ` [PATCH v2 1/1] input: bbnsm_pwrkey: " Frank Li
2024-07-16 21:00 ` Frank Li
2024-08-12 17:35 ` [PATCH 1/2] input: keyboard: snvs_pwrkey: Enable clock when accessing HP* registers Dmitry Torokhov
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=20240716205612.1502608-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=dmitry.torokhov@gmail.com \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yibin.gong@nxp.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
all inboxes | Powered by JetHome®