public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Jonathan Marek <jonathan@marek.ca>
Cc: bjorn.andersson@linaro.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: qcom_rpm: write fw_version to CTRL_REG
Date: Thu, 15 Nov 2018 08:31:21 +0000	[thread overview]
Message-ID: <20181115083121.GI3513@dell> (raw)
In-Reply-To: <20181114224201.16225-1-jonathan@marek.ca>

On Wed, 14 Nov 2018, Jonathan Marek wrote:

> downstream driver does this, and it is required on msm8060 (hp touchpad)

You can leave the bit about the downstream driver.

Please expand your commit message.  Why is it required?  What happens
if you don't have it?  What problem does it solve?  Exactly what is
happening to the H/W?

> Signed-off-by: Jonathan Marek <jonathan@marek.ca>
> ---
>  drivers/mfd/qcom_rpm.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/mfd/qcom_rpm.c b/drivers/mfd/qcom_rpm.c
> index 52fafea06067..8d420c37b2a6 100644
> --- a/drivers/mfd/qcom_rpm.c
> +++ b/drivers/mfd/qcom_rpm.c
> @@ -638,6 +638,10 @@ static int qcom_rpm_probe(struct platform_device *pdev)
>  		return -EFAULT;
>  	}
>  
> +	writel(fw_version[0], RPM_CTRL_REG(rpm, 0));
> +	writel(fw_version[1], RPM_CTRL_REG(rpm, 1));
> +	writel(fw_version[2], RPM_CTRL_REG(rpm, 2));
> +
>  	dev_info(&pdev->dev, "RPM firmware %u.%u.%u\n", fw_version[0],
>  							fw_version[1],
>  							fw_version[2]);

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2018-11-15  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 22:42 [PATCH] mfd: qcom_rpm: write fw_version to CTRL_REG Jonathan Marek
2018-11-15  8:31 ` Lee Jones [this message]
2018-11-19 19:53 ` [PATCH v2] " Jonathan Marek
2018-11-27 13:03   ` Lee Jones

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=20181115083121.GI3513@dell \
    --to=lee.jones@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=jonathan@marek.ca \
    --cc=linux-kernel@vger.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