From: Vinod <vkoul@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 4/5] input: pm8941-pwrkey: Abstract register offsets and event code
Date: Sat, 23 Jun 2018 10:02:58 +0530 [thread overview]
Message-ID: <20180623043258.GT27187@vkoul-mobl> (raw)
In-Reply-To: <20180622185236.GD92912@dtor-ws>
On 22-06-18, 11:52, Dmitry Torokhov wrote:
> > static int pm8941_reboot_notify(struct notifier_block *nb,
> > @@ -124,7 +132,8 @@ static irqreturn_t pm8941_pwrkey_irq(int irq, void *_data)
> > if (error)
> > return IRQ_HANDLED;
> >
> > - input_report_key(pwrkey->input, KEY_POWER, !!(sts & PON_KPDPWR_N_SET));
> > + input_report_key(pwrkey->input, pwrkey->code,
> > + !!(sts & pwrkey->data->status_bit));
>
> Since we are changing this: input core will normalize the value for you,
> no need for doing double negation here.
Okay will do, since this "should" be explained that input core handles
it, do you recommend and separate patch for that?
> > @@ -190,8 +209,13 @@ static int pm8941_pwrkey_probe(struct platform_device *pdev)
> >
> > error = of_property_read_u32(pdev->dev.of_node, "reg",
> > &pwrkey->baseaddr);
> > - if (error)
> > - return error;
> > + if (error) {
> > + /* check if parent has reg before bailing */
> > + error = of_property_read_u32(pdev->dev.parent->of_node,
> > + "reg", &pwrkey->baseaddr);
> > + if (error)
> > + return error;
>
> I do not want us blindly look up into parent for individual properties.
> We need to decide early on if we are dealing with subnode or older
> binding and stick to it.
okay will do.
> > error = regmap_read(pwrkey->regmap, pwrkey->baseaddr + PON_REV2,
> > &pwrkey->revision);
> > @@ -200,13 +224,20 @@ static int pm8941_pwrkey_probe(struct platform_device *pdev)
> > return error;
> > }
> >
> > + error = of_property_read_u32(pdev->dev.of_node, "linux,code",
> > + &pwrkey->code);
> > + if (error) {
> > + dev_err(&pdev->dev, "no linux,code assuming power%d\n", error);
>
> This is not an error. dev_dbg or dev_info at most.
okay will change
--
~Vinod
next prev parent reply other threads:[~2018-06-23 4:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 14:35 [PATCH 0/5]: input: pm8941-pwrkey: Add support for reboot reason Vinod Koul
2018-06-18 14:35 ` [PATCH 1/5] dt-bindings: power: reset: Add qcom pon binding Vinod Koul
2018-06-22 20:58 ` Bjorn Andersson
2018-06-23 4:29 ` Vinod
2018-06-18 14:35 ` [PATCH 2/5] power: reset: qcom-pon: Add Qcom PON driver Vinod Koul
2018-06-18 14:35 ` [PATCH 3/5] dt-bindings: Input: Add additional property to qcom pwrkey Vinod Koul
2018-06-22 20:59 ` Bjorn Andersson
2018-06-18 14:35 ` [PATCH 4/5] input: pm8941-pwrkey: Abstract register offsets and event code Vinod Koul
2018-06-22 18:52 ` Dmitry Torokhov
2018-06-23 4:32 ` Vinod [this message]
2018-06-22 21:10 ` Bjorn Andersson
2018-06-23 4:34 ` Vinod
2018-06-18 14:35 ` [PATCH 5/5] input: pm8941-pwrkey: Add resin entry Vinod Koul
2018-06-22 21:00 ` Bjorn Andersson
2018-06-22 18:53 ` [PATCH 0/5]: input: pm8941-pwrkey: Add support for reboot reason 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=20180623043258.GT27187@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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