linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>,
	dmitry.torokhov@gmail.com, corbet@lwn.net, sre@kernel.org,
	robh+dt@kernel.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, collinsd@codeaurora.org,
	bjorn.andersson@linaro.org, swboyd@chromium.org,
	skakit@codeaurora.org, linux-doc@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses
Date: Fri, 15 Apr 2022 00:18:53 +0300	[thread overview]
Message-ID: <d9afa206-7f57-81bb-8c69-5928dccd41b5@linaro.org> (raw)
In-Reply-To: <20220411200506.22891-4-quic_amelende@quicinc.com>

On 11/04/2022 23:05, Anjelique Melendez wrote:
> Currently, PON address is read from the "reg" property. For PON GEN3,
> which starts with PMK8350, the "reg" property will have both the PON
> HLOS and PON PBS addesses defined. Add support so that all PON
> generations can be configured.
> 
> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> ---
>   drivers/input/misc/pm8941-pwrkey.c | 31 +++++++++++++++++++++++-------
>   1 file changed, 24 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/input/misc/pm8941-pwrkey.c b/drivers/input/misc/pm8941-pwrkey.c
> index e0240db12d4f..43106e4cfd23 100644
> --- a/drivers/input/misc/pm8941-pwrkey.c
> +++ b/drivers/input/misc/pm8941-pwrkey.c
> @@ -12,6 +12,7 @@
>   #include <linux/log2.h>
>   #include <linux/module.h>
>   #include <linux/of.h>
> +#include <linux/of_address.h>
>   #include <linux/of_device.h>
>   #include <linux/platform_device.h>
>   #include <linux/reboot.h>
> @@ -44,6 +45,7 @@ struct pm8941_data {
>   	unsigned int	status_bit;
>   	bool		supports_ps_hold_poff_config;
>   	bool		supports_debounce_config;
> +	bool		has_pon_pbs;
>   	const char	*name;
>   	const char	*phys;
>   };
> @@ -52,6 +54,7 @@ struct pm8941_pwrkey {
>   	struct device *dev;
>   	int irq;
>   	u32 baseaddr;
> +	u32 pon_pbs_baseaddr;
>   	struct regmap *regmap;
>   	struct input_dev *input;
>   
> @@ -167,6 +170,8 @@ static int pm8941_pwrkey_probe(struct platform_device *pdev)
>   	struct pm8941_pwrkey *pwrkey;
>   	bool pull_up;
>   	struct device *parent;
> +	struct device_node *regmap_node;
> +	const __be32 *addr;
>   	u32 req_delay;
>   	int error;
>   
> @@ -188,8 +193,10 @@ static int pm8941_pwrkey_probe(struct platform_device *pdev)
>   	pwrkey->data = of_device_get_match_data(&pdev->dev);
>   
>   	parent = pdev->dev.parent;
> +	regmap_node = pdev->dev.of_node;
>   	pwrkey->regmap = dev_get_regmap(parent, NULL);
>   	if (!pwrkey->regmap) {
> +		regmap_node = parent->of_node;
>   		/*
>   		 * We failed to get regmap for parent. Let's see if we are
>   		 * a child of pon node and read regmap and reg from its
> @@ -200,15 +207,21 @@ static int pm8941_pwrkey_probe(struct platform_device *pdev)
>   			dev_err(&pdev->dev, "failed to locate regmap\n");
>   			return -ENODEV;
>   		}
> +	}
>   
> -		error = of_property_read_u32(parent->of_node,
> -					     "reg", &pwrkey->baseaddr);
> -	} else {
> -		error = of_property_read_u32(pdev->dev.of_node, "reg",
> -					     &pwrkey->baseaddr);
> +	addr = of_get_address(regmap_node, 0, NULL, NULL);
> +	if (!addr) {
> +		dev_err(&pdev->dev, "reg property missing\n");
> +		return -EINVAL;
> +	}
> +	pwrkey->baseaddr = be32_to_cpup(addr);
> +
> +	if (pwrkey->data->has_pon_pbs) {
> +		/* PON_PBS base address is optional */
> +		addr = of_get_address(regmap_node, 1, NULL, NULL);
> +		if (addr)
> +			pwrkey->pon_pbs_baseaddr = be32_to_cpup(addr);
>   	}
> -	if (error)
> -		return error;
>   
>   	pwrkey->irq = platform_get_irq(pdev, 0);
>   	if (pwrkey->irq < 0)
> @@ -316,6 +329,7 @@ static const struct pm8941_data pwrkey_data = {
>   	.phys = "pm8941_pwrkey/input0",
>   	.supports_ps_hold_poff_config = true,
>   	.supports_debounce_config = true,
> +	.has_pon_pbs = false,
>   };
>   
>   static const struct pm8941_data resin_data = {
> @@ -325,6 +339,7 @@ static const struct pm8941_data resin_data = {
>   	.phys = "pm8941_resin/input0",
>   	.supports_ps_hold_poff_config = true,
>   	.supports_debounce_config = true,
> +	.has_pon_pbs = false,

No need to declare that a field is false. Just skip this completely.

>   };
>   
>   static const struct pm8941_data pon_gen3_pwrkey_data = {
> @@ -333,6 +348,7 @@ static const struct pm8941_data pon_gen3_pwrkey_data = {
>   	.phys = "pmic_pwrkey/input0",
>   	.supports_ps_hold_poff_config = false,
>   	.supports_debounce_config = false,
> +	.has_pon_pbs = true,
>   };
>   
>   static const struct pm8941_data pon_gen3_resin_data = {
> @@ -341,6 +357,7 @@ static const struct pm8941_data pon_gen3_resin_data = {
>   	.phys = "pmic_resin/input0",
>   	.supports_ps_hold_poff_config = false,
>   	.supports_debounce_config = false,
> +	.has_pon_pbs = true,
>   };
>   
>   static const struct of_device_id pm8941_pwr_key_id_table[] = {


-- 
With best wishes
Dmitry

  reply	other threads:[~2022-04-14 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 20:05 [PATCH v5 0/5] Extend pm8941-pwrkey driver Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 1/5] dt-bindings: power: reset: qcom-pon: update "reg" property details Anjelique Melendez
2022-04-14 15:34   ` Rob Herring
2022-04-15 18:44     ` Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 2/5] input: misc: pm8941-pwrkey: fix error message Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 3/5] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses Anjelique Melendez
2022-04-14 21:18   ` Dmitry Baryshkov [this message]
2022-04-15 18:46     ` Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 4/5] input: misc: pm8941-pwrkey: add software key press debouncing support Anjelique Melendez
2022-04-11 20:05 ` [PATCH v5 5/5] input: misc: pm8941-pwrkey: simulate missed key press events Anjelique Melendez

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=d9afa206-7f57-81bb-8c69-5928dccd41b5@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=collinsd@codeaurora.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_amelende@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=skakit@codeaurora.org \
    --cc=sre@kernel.org \
    --cc=swboyd@chromium.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).