[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170718071936.llnpgwqmgzt2axea@dell>
Date: Tue, 18 Jul 2017 08:19:36 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Quentin Schulz <quentin.schulz@...e-electrons.com>
Cc: dmitry.torokhov@...il.com, wens@...e.org, hdegoede@...hat.com,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
thomas.petazzoni@...e-electrons.com,
maxime.ripard@...e-electrons.com
Subject: Re: [PATCH 2/2] mfd: axp20x: use correct platform device id for many
PEK
On Mon, 17 Jul 2017, 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, let's use the platform device id with the correct values.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@...e-electrons.com>
> ---
> drivers/mfd/axp20x.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
Patch is find, but are these names reference from platform data
anywhere i.e. are we going to break anything by applying it?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists