[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ddd06c43-026e-2801-dc36-053d469e43f3@gmail.com>
Date: Fri, 31 Aug 2018 14:05:59 +0200
From: Philipp Rossak <embed3d@...il.com>
To: Maxime Ripard <maxime.ripard@...tlin.com>
Cc: lee.jones@...aro.org, robh+dt@...nel.org, mark.rutland@....com,
wens@...e.org, linux@...linux.org.uk, jic23@...nel.org,
knaack.h@....de, lars@...afoo.de, pmeerw@...erw.net,
eugen.hristev@...rochip.com, rdunlap@...radead.org,
vilhelm.gray@...il.com, clabbe.montjoie@...il.com,
quentin.schulz@...tlin.com, geert+renesas@...der.be,
lukas@...ner.de, icenowy@...c.io, arnd@...db.de,
broonie@...nel.org, arnaud.pouliquen@...com,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-sunxi@...glegroups.com
Subject: Re: [PATCH v3 20/30] iio: adc: sun4i-gpadc-iio: rework: device
specific suspend & resume
On 31.08.2018 11:09, Maxime Ripard wrote:
>> +static int sun4i_ths_suspend(struct sun4i_gpadc_iio *info)
> suspend is already a hook in the kernel, which hasn't the same meaning
> than runtime_suspend (and the same applies to resume), so we'd rather
> pick a better name. And all the functions (and the driver) use gpadc,
> please continue to use that prefix.
I agree.
For the newer sensors (from H3) the Sensor is referenced in the
datasheets as Thermal Sensor short THS. So I would like to use for the
newer sensors that prefix. Is that ok?
Philipp
Powered by blists - more mailing lists