All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Boirie <gregor.boirie@parrot.com>
To: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Vlad Dogaru <ddvlad@gmail.com>,
	Ludovic Tancerel <ludovic.tancerel@maplehightech.com>,
	Marek Vasut <marex@denx.de>,
	Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH v4 1/1] iio:pressure: initial zpa2326 barometer support
Date: Tue, 13 Sep 2016 09:55:29 +0200	[thread overview]
Message-ID: <57D7B0F1.6030607@parrot.com> (raw)
In-Reply-To: <d6122349-5e8c-6708-b5af-a38f9e8bb898@kernel.org>

Hi,

On 09/10/2016 05:37 PM, Jonathan Cameron wrote:
> On 09/09/16 16:01, Gregor Boirie wrote:
>> Introduce driver for Murata ZPA2326 pressure and temperature sensor:
>> http://www.murata.com/en-us/products/productdetail?partno=ZPA2326-0311A-R
>>
>> Signed-off-by: Gregor Boirie <gregor.boirie@parrot.com>
> This looks pretty good to me now.  A few minor bits and bobs inline.
>
> I almost took it as is, but would like to have it sit on the list
> in it's current form for a few more days anyway so might as well get
> these few corners tidied up!
[...]
>
> +/*
> + * Debugfs stuff
> + *
> + * We want to prevent debugfs hooks from altering configuration while chip
> + * sampling is ongoing to preserve data consistency. Moreover, a few registers,
> + * when read, change hardware state, e.g. interrupt acknowlege on read. This is
> + * why debugfs read and write hooks acquire exclusive access to register space.
> + *
> + * Also note this is mostly unusable with power management enabled systems since
> + * registers content is lost during power off -> on transitions.
> + */
> It would be nice perhaps to tighten up the range of addresses that
> we are protecting.  Thus allow reading of any addresses that are not
> 'fragile'.  Only supported limited debug access is hardly a big
> issue however ;)
Quite frankly, I wonder if this debugfs stuff should not be thrown away 
given that
regmap already provides a way to access registers over debugfs (with 
very limited
protection...).
What do you think ?

[...]

Regards,
Grégor.

WARNING: multiple messages have this Message-ID (diff)
From: Gregor Boirie <gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>,
	Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
	Peter Meerwald-Stadler
	<pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Akinobu Mita
	<akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Linus Walleij
	<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Vlad Dogaru <ddvlad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Ludovic Tancerel
	<ludovic.tancerel-sbt5i+FMW2pmsedzY7GhzwC/G2K4zDHf@public.gmane.org>,
	Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
	Crestez Dan Leonard
	<leonard.crestez-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v4 1/1] iio:pressure: initial zpa2326 barometer support
Date: Tue, 13 Sep 2016 09:55:29 +0200	[thread overview]
Message-ID: <57D7B0F1.6030607@parrot.com> (raw)
In-Reply-To: <d6122349-5e8c-6708-b5af-a38f9e8bb898-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

Hi,

On 09/10/2016 05:37 PM, Jonathan Cameron wrote:
> On 09/09/16 16:01, Gregor Boirie wrote:
>> Introduce driver for Murata ZPA2326 pressure and temperature sensor:
>> http://www.murata.com/en-us/products/productdetail?partno=ZPA2326-0311A-R
>>
>> Signed-off-by: Gregor Boirie <gregor.boirie-ITF29qwbsa/QT0dZR+AlfA@public.gmane.org>
> This looks pretty good to me now.  A few minor bits and bobs inline.
>
> I almost took it as is, but would like to have it sit on the list
> in it's current form for a few more days anyway so might as well get
> these few corners tidied up!
[...]
>
> +/*
> + * Debugfs stuff
> + *
> + * We want to prevent debugfs hooks from altering configuration while chip
> + * sampling is ongoing to preserve data consistency. Moreover, a few registers,
> + * when read, change hardware state, e.g. interrupt acknowlege on read. This is
> + * why debugfs read and write hooks acquire exclusive access to register space.
> + *
> + * Also note this is mostly unusable with power management enabled systems since
> + * registers content is lost during power off -> on transitions.
> + */
> It would be nice perhaps to tighten up the range of addresses that
> we are protecting.  Thus allow reading of any addresses that are not
> 'fragile'.  Only supported limited debug access is hardly a big
> issue however ;)
Quite frankly, I wonder if this debugfs stuff should not be thrown away 
given that
regmap already provides a way to access registers over debugfs (with 
very limited
protection...).
What do you think ?

[...]

Regards,
Grégor.

  reply	other threads:[~2016-09-13  7:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 15:00 [PATCH v4 0/1] iio: devm helpers and Murata zpa2326 barometer support Gregor Boirie
2016-09-09 15:00 ` Gregor Boirie
2016-09-09 15:01 ` [PATCH v4 1/1] iio:pressure: initial " Gregor Boirie
2016-09-09 15:01   ` Gregor Boirie
2016-09-10 15:37   ` Jonathan Cameron
2016-09-10 15:37     ` Jonathan Cameron
2016-09-13  7:55     ` Gregor Boirie [this message]
2016-09-13  7:55       ` Gregor Boirie
2016-09-13  8:52       ` jic23
2016-09-13  8:52         ` jic23-tko9wxEg+fIOOJlXag/Snyp2UmYkHbXO

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=57D7B0F1.6030607@parrot.com \
    --to=gregor.boirie@parrot.com \
    --cc=akinobu.mita@gmail.com \
    --cc=ddvlad@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=leonard.crestez@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=ludovic.tancerel@maplehightech.com \
    --cc=marex@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.