From: Chen-Yu Tsai <wens@csie.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chen-Yu Tsai <wens@csie.org>, Hans de Goede <hdegoede@redhat.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH 0/2] use correct values for startup time bits for AXP22X/AXP8XX PEKs
Date: Tue, 18 Jul 2017 15:40:27 +0800 [thread overview]
Message-ID: <CAGb2v66Y6D+qsmuUifU5md433F25=ZqaeXRG4hVULnaZGG+b_w@mail.gmail.com> (raw)
In-Reply-To: <1f2d37bd-b4a1-2653-c1c6-6dced95b814a@free-electrons.com>
On Tue, Jul 18, 2017 at 3:25 PM, Quentin Schulz
<quentin.schulz@free-electrons.com> wrote:
> Hi Lee,
>
> On 18/07/2017 09:18, Lee Jones wrote:
>> On Mon, 17 Jul 2017, Quentin Schulz wrote:
>>
>>> Hi all,
>>>
>>> On 17/07/2017 11:53, Quentin Schulz wrote:
>>>> According to their datasheets, the AXP221, AXP223, AXP288, AXP803,
>>>> AXP809 and AXP813 PEK have different values for startup time bits from
>>>> the AXP20X PEK (which are currently used for all the aforementioned PMICs).
>>>>
>>>> This patch series adds support for platform_device_id to axp20x-pek driver
>>>> to support different startup time bits depending on PMIC's variant and set
>>>> the correct platform_device_id in the mfd.
>>>>
>>>> This has been tested on AXP813. To perform the test, modify the value of
>>>> startup and/or shutdown of the pek in sysfs. Press the button soldered to
>>>> PEK input of the AXP the amount of time you set in sysfs. The PMIC shuts
>>>> down the board without needing to unplug any power supply. Press PEK button
>>>> the amount of time you set in sysfs for startup and the PMIC will start the
>>>> board. Note that the time bits are obivoulsy hardware reset to their
>>>> default when you unplug all power supplies from the board.
>>>>
>>>
>>> I forgot to add that it depends on this patch series (particularly the
>>> third patch (3/6) "mfd: axp20x: Add support for AXP813 PMIC") from
>>> Chen-Yu:
>>> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1428284.html
>>
>> So you are going to re-send?
>>
>
> You put your acked-by just yesterday on this patch. Do I need to resend
> it anyway?
>
> The link I provided seems to be really slow/not working today, so I give
> you another one for reference: https://patchwork.kernel.org/patch/9803439/
Or rather, would you like me to merge the AXP813 changes into my next
version, and you resend the rest for faster separate inclusion?
ChenYu
> Thanks,
> Quentin
>
>>>> Quentin Schulz (2):
>>>> Input: axp20x-pek: add support for AXP221 PEK
>>>> mfd: axp20x: use correct platform device id for many PEK
>>>>
>>>> drivers/input/misc/axp20x-pek.c | 62 ++++++++++++++++++++++++++++++++++-------
>>>> drivers/mfd/axp20x.c | 12 ++++----
>>>> 2 files changed, 58 insertions(+), 16 deletions(-)
>>>>
>>>
>>
>
> --
> Quentin Schulz, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2017-07-18 7:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 9:53 [PATCH 0/2] use correct values for startup time bits for AXP22X/AXP8XX PEKs Quentin Schulz
2017-07-17 9:53 ` [PATCH 1/2] Input: axp20x-pek: add support for AXP221 PEK Quentin Schulz
2017-07-17 11:29 ` Maxime Ripard
2017-07-18 7:36 ` Quentin Schulz
2017-07-18 7:57 ` Maxime Ripard
2017-07-18 8:10 ` Quentin Schulz
2017-07-17 9:53 ` [PATCH 2/2] mfd: axp20x: use correct platform device id for many PEK Quentin Schulz
2017-07-18 7:19 ` Lee Jones
2017-07-18 7:43 ` Quentin Schulz
2017-07-18 9:49 ` Lee Jones
2017-07-18 10:04 ` Quentin Schulz
2017-07-18 10:26 ` Lee Jones
2017-07-18 10:28 ` Lee Jones
2017-07-17 11:15 ` [PATCH 0/2] use correct values for startup time bits for AXP22X/AXP8XX PEKs Quentin Schulz
2017-07-18 7:18 ` Lee Jones
2017-07-18 7:25 ` Quentin Schulz
2017-07-18 7:40 ` Chen-Yu Tsai [this message]
2017-07-18 9:53 ` Lee Jones
2017-07-19 7:24 ` Chen-Yu Tsai
2017-07-19 7:46 ` 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='CAGb2v66Y6D+qsmuUifU5md433F25=ZqaeXRG4hVULnaZGG+b_w@mail.gmail.com' \
--to=wens@csie.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=quentin.schulz@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).