From: Srinivas Kandagatla <srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2 2/2] nvmem: mxs-ocotp: remove nvmem regmap dependency
Date: Mon, 2 May 2016 19:03:41 +0100 [thread overview]
Message-ID: <5727967D.8030202@linaro.org> (raw)
In-Reply-To: <CAOMZO5DoqdOPM+i6D37PviCbiDSc3OV2rz8vGRi0mqV4uBvgaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/05/16 17:15, Fabio Estevam wrote:
> On Mon, May 2, 2016 at 12:22 PM, Srinivas Kandagatla
> <srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
>> This patch moves to nvmem support in the driver to use callback
>> instead of regmap.
>
> It would be nice if you could explain the reason for doing this.
>
Sure, Basically using regmap raw accessors in a generic way in nvmem
core broken nvmem providers based on regmap mmio bus.
More details at
https://groups.google.com/forum/#!topic/linux.kernel/LT3hM-GOf1k
thanks,
srini
WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] nvmem: mxs-ocotp: remove nvmem regmap dependency
Date: Mon, 2 May 2016 19:03:41 +0100 [thread overview]
Message-ID: <5727967D.8030202@linaro.org> (raw)
In-Reply-To: <CAOMZO5DoqdOPM+i6D37PviCbiDSc3OV2rz8vGRi0mqV4uBvgaw@mail.gmail.com>
On 02/05/16 17:15, Fabio Estevam wrote:
> On Mon, May 2, 2016 at 12:22 PM, Srinivas Kandagatla
> <srinivas.kandagatla@linaro.org> wrote:
>> This patch moves to nvmem support in the driver to use callback
>> instead of regmap.
>
> It would be nice if you could explain the reason for doing this.
>
Sure, Basically using regmap raw accessors in a generic way in nvmem
core broken nvmem providers based on regmap mmio bus.
More details at
https://groups.google.com/forum/#!topic/linux.kernel/LT3hM-GOf1k
thanks,
srini
WARNING: multiple messages have this Message-ID (diff)
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mediatek@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] nvmem: mxs-ocotp: remove nvmem regmap dependency
Date: Mon, 2 May 2016 19:03:41 +0100 [thread overview]
Message-ID: <5727967D.8030202@linaro.org> (raw)
In-Reply-To: <CAOMZO5DoqdOPM+i6D37PviCbiDSc3OV2rz8vGRi0mqV4uBvgaw@mail.gmail.com>
On 02/05/16 17:15, Fabio Estevam wrote:
> On Mon, May 2, 2016 at 12:22 PM, Srinivas Kandagatla
> <srinivas.kandagatla@linaro.org> wrote:
>> This patch moves to nvmem support in the driver to use callback
>> instead of regmap.
>
> It would be nice if you could explain the reason for doing this.
>
Sure, Basically using regmap raw accessors in a generic way in nvmem
core broken nvmem providers based on regmap mmio bus.
More details at
https://groups.google.com/forum/#!topic/linux.kernel/LT3hM-GOf1k
thanks,
srini
next prev parent reply other threads:[~2016-05-02 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 15:22 [PATCH v2 0/2] nvmem: remove regmap dependency Srinivas Kandagatla
2016-05-02 15:22 ` Srinivas Kandagatla
2016-05-02 15:22 ` Srinivas Kandagatla
2016-05-02 15:22 ` [PATCH v2 1/2] nvmem: mtk-efuse: remove nvmem " Srinivas Kandagatla
2016-05-02 15:22 ` Srinivas Kandagatla
2016-05-02 15:22 ` [PATCH v2 2/2] nvmem: mxs-ocotp: " Srinivas Kandagatla
2016-05-02 15:22 ` Srinivas Kandagatla
2016-05-02 15:22 ` Srinivas Kandagatla
2016-05-02 16:15 ` Fabio Estevam
2016-05-02 16:15 ` Fabio Estevam
[not found] ` <CAOMZO5DoqdOPM+i6D37PviCbiDSc3OV2rz8vGRi0mqV4uBvgaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-02 18:03 ` Srinivas Kandagatla [this message]
2016-05-02 18:03 ` Srinivas Kandagatla
2016-05-02 18:03 ` Srinivas Kandagatla
2016-05-02 16:17 ` Fabio Estevam
2016-05-02 16:17 ` Fabio Estevam
[not found] ` <1462202578-15433-3-git-send-email-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-05-02 16:26 ` Stefan Wahren
2016-05-02 16:26 ` Stefan Wahren
2016-05-02 16:26 ` Stefan Wahren
2016-05-02 18:06 ` Srinivas Kandagatla
2016-05-02 18:06 ` Srinivas Kandagatla
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=5727967D.8030202@linaro.org \
--to=srinivas.kandagatla-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=stefan.wahren-eS4NqCHxEME@public.gmane.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.