[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGb2v65xoUZA+AGb+1LEba-ccmDdLo6YyAB1nqo2uKUN7x=2kA@mail.gmail.com>
Date: Mon, 14 Aug 2017 18:03:44 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Quentin Schulz <quentin.schulz@...e-electrons.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Chen-Yu Tsai <wens@...e.org>, Lee Jones <lee.jones@...aro.org>,
Hans de Goede <hdegoede@...hat.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>
Subject: Re: [PATCH v3 1/2] Input: axp20x-pek: use driver_data of
platform_device_id instead of extended attributes
On Wed, Aug 9, 2017 at 5:45 PM, Quentin Schulz
<quentin.schulz@...e-electrons.com> wrote:
> To prepare an upcoming patch adding support for another PMIC that has
> different startup and shutdown time, use driver_data of
> platform_device_id instead of a fixed extended device attribute.
>
> By doing so, we also remove a lot of nested structures that aren't
> useful.
>
> With this patch, a new PMIC can be easily supported by just filling
> correctly its ax20x_info structure and adding a platform_device_id.
>
> Moreover, since we get rid of extended attributes, rename
> axp20x_store_ext_attr to axp20x_store_attr and axp20x_show_ext_attr to
> axp20x_show_attr.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@...e-electrons.com>
Acked-by: Chen-Yu Tsai <wens@...e.org>
[...]
> +
> +DEVICE_ATTR(startup, 0644, axp20x_show_attr_startup, axp20x_store_attr_startup);
> +DEVICE_ATTR(shutdown, 0644, axp20x_show_attr_shutdown,
> + axp20x_store_attr_shutdown);
>
You could use DEVICE_ATTR_RW(...) if you renamed the function names to
fit the macro if you wanted.
Powered by blists - more mailing lists