linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/9] Input: pmic8xxx-pwrkey - Migrate to regmap APIs
Date: Wed, 26 Feb 2014 16:20:03 -0800	[thread overview]
Message-ID: <530E84B3.8020608@codeaurora.org> (raw)
In-Reply-To: <20140227001358.GF18563@joshc.qualcomm.com>

On 02/26/14 16:13, Josh Cartwright wrote:
> On Wed, Feb 26, 2014 at 04:05:40PM -0800, Stephen Boyd wrote:
>> On 02/26/14 15:59, Josh Cartwright wrote:
>>> On Wed, Feb 26, 2014 at 11:05:54AM -0800, Stephen Boyd wrote:
>>>> Use the regmap APIs for this driver instead of custom pm8xxx
>>>> APIs. This breaks this driver's dependency on the pm8xxx APIs and
>>>> allows us to easily port it to other bus protocols in the future.
>>>>
>>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>>> ---
>>>>  drivers/input/misc/pmic8xxx-pwrkey.c | 4 ++++
>>>>  1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/drivers/input/misc/pmic8xxx-pwrkey.c b/drivers/input/misc/pmic8xxx-pwrkey.c
>>>> index 0e1a05f95858..cf6125dc3b51 100644
>>>> --- a/drivers/input/misc/pmic8xxx-pwrkey.c
>>>> +++ b/drivers/input/misc/pmic8xxx-pwrkey.c
>>>> @@ -120,6 +120,10 @@ static int pmic8xxx_pwrkey_probe(struct platform_device *pdev)
>>>>  		return -ENOMEM;
>>>>  	}
>>>>  
>>>> +	regmap = dev_get_regmap(pdev->dev.parent, NULL);
>>>> +	if (!regmap)
>>>> +		return -ENODEV;
>>>> +
>>> This looks really weird.  A previous version of patch was included in
>>> v3.14-rc1 (1e63bd9cc4), which already included a very similar hunk...
>>>
>>> Maybe the fact that the hunk isn't identical is why a rebase didn't drop
>>> it (and instead, now if this gets merged, we'll have unnecessary
>>> duplication).
>>>
>> Ah yeah, sorry about that. This patch should just be ignored. I don't
>> think it affects anything else in the series?
> Yep, I think this can be safely ignored.
>
> However, I think it needs to be made clear that your if "Modernize pm8921
> with irqdomains, regmap, DT" lands before this patchset, this will start
> breaking randconfig builds.  It isn't clear to me how this dependency
> should be handled.
>

Hmm? If pm8921 lands before this what build breakage is there? The
pm8xxx_read/write APIs are still exposed.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2014-02-27  0:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 19:05 [PATCH v3 0/9] Use regmap+devm+DT in pm8xxx input drivers Stephen Boyd
2014-02-26 19:05 ` [PATCH v3 1/9] Input: pmic8xxx-pwrkey - Migrate to regmap APIs Stephen Boyd
2014-02-26 23:59   ` Josh Cartwright
2014-02-27  0:05     ` Stephen Boyd
2014-02-27  0:13       ` Josh Cartwright
2014-02-27  0:20         ` Stephen Boyd [this message]
2014-02-27  0:30           ` Josh Cartwright
2014-02-27  0:43             ` Stephen Boyd
2014-02-27  2:31               ` Josh Cartwright
2014-02-26 19:05 ` [PATCH v3 2/9] Input: pmic8xxx-keypad - Migrate to devm_* APIs Stephen Boyd
2014-02-27  0:09   ` Josh Cartwright
2014-02-27  0:20     ` Stephen Boyd
2014-02-26 19:05 ` [PATCH v3 3/9] Input: pmic8xxx-keypad - Migrate to regmap APIs Stephen Boyd
2014-02-26 19:05 ` [PATCH v3 4/9] Input: pmic8xxx-pwrkey - Migrate to DT Stephen Boyd
2014-02-26 19:05 ` [PATCH v3 5/9] Input: pm8xxx-vibrator - Add DT match table Stephen Boyd
2014-02-26 19:05 ` [PATCH v3 6/9] Input: pmic8xxx-keypad - Migrate to DT Stephen Boyd
2014-02-26 19:06 ` [PATCH v3 7/9] devicetree: bindings: Document PM8921/8058 keypads Stephen Boyd
2014-02-26 19:06 ` [PATCH v3 8/9] devicetree: bindings: Document PM8921/8058 power keys Stephen Boyd
2014-02-26 19:06 ` [PATCH v3 9/9] devicetree: bindings: Document PM8921/8058 vibrators Stephen Boyd

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=530E84B3.8020608@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=joshc@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).