All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-mediatek@lists.infradead.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] nvmem: remove regmap dependency
Date: Wed, 18 May 2016 16:30:01 +0200	[thread overview]
Message-ID: <573C7C69.1050301@i2se.com> (raw)
In-Reply-To: <1462214174-469-1-git-send-email-srinivas.kandagatla@linaro.org>

Hi Srinivas,

Am 02.05.2016 um 20:36 schrieb Srinivas Kandagatla:
> Hi Greg, 
>
> This is v3 patchset for the leftover 2 patches for nvmem regmap
> removal series [1]. These patches are based on char-misc tree.
>
> nvmem uses regmap_raw_read/write apis to read/write data from providers,
> With recent patch 922a9f936e40 ("regmap: mmio: Convert to regmap_bus
> and fix accessor usage") nvmem providers based on regmap-mmio stopped
> working, as nvmem core was using raw accessors.
> This issue can be fixed temporarly by moving to other regmap apis,
> but we might hit same issue in future, and regmap looks like an
> overdo for nvmem. Moving to interfaces based on read/write callbacks
> from providers would be more robust.

i noticed that Documentation/nvmem/nvmem.txt also needs a fix after
removing regmap dependency.

WARNING: multiple messages have this Message-ID (diff)
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] nvmem: remove regmap dependency
Date: Wed, 18 May 2016 16:30:01 +0200	[thread overview]
Message-ID: <573C7C69.1050301@i2se.com> (raw)
In-Reply-To: <1462214174-469-1-git-send-email-srinivas.kandagatla@linaro.org>

Hi Srinivas,

Am 02.05.2016 um 20:36 schrieb Srinivas Kandagatla:
> Hi Greg, 
>
> This is v3 patchset for the leftover 2 patches for nvmem regmap
> removal series [1]. These patches are based on char-misc tree.
>
> nvmem uses regmap_raw_read/write apis to read/write data from providers,
> With recent patch 922a9f936e40 ("regmap: mmio: Convert to regmap_bus
> and fix accessor usage") nvmem providers based on regmap-mmio stopped
> working, as nvmem core was using raw accessors.
> This issue can be fixed temporarly by moving to other regmap apis,
> but we might hit same issue in future, and regmap looks like an
> overdo for nvmem. Moving to interfaces based on read/write callbacks
> from providers would be more robust.

i noticed that Documentation/nvmem/nvmem.txt also needs a fix after
removing regmap dependency.

  parent reply	other threads:[~2016-05-18 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 18:36 [PATCH v3 0/2] nvmem: remove regmap dependency Srinivas Kandagatla
2016-05-02 18:36 ` Srinivas Kandagatla
2016-05-02 18:36 ` [PATCH v3 1/2] nvmem: mtk-efuse: remove nvmem " Srinivas Kandagatla
2016-05-02 18:36   ` Srinivas Kandagatla
     [not found] ` <1462214174-469-1-git-send-email-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-05-02 18:36   ` [PATCH v3 2/2] nvmem: mxs-ocotp: " Srinivas Kandagatla
2016-05-02 18:36     ` Srinivas Kandagatla
2016-05-02 18:36     ` Srinivas Kandagatla
     [not found]     ` <1462214174-469-3-git-send-email-srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-05-04 11:03       ` Stefan Wahren
2016-05-04 11:03         ` Stefan Wahren
2016-05-04 11:03         ` Stefan Wahren
2016-05-18 14:30 ` Stefan Wahren [this message]
2016-05-18 14:30   ` [PATCH v3 0/2] nvmem: remove " Stefan Wahren
2016-05-18 14:36   ` Srinivas Kandagatla
2016-05-18 14:36     ` Srinivas Kandagatla
2016-06-01  8:27 ` Stefan Wahren
2016-06-01  8:27   ` Stefan Wahren
2016-06-01 17:55   ` Greg Kroah-Hartman
2016-06-01 17:55     ` Greg Kroah-Hartman
     [not found]     ` <20160601175542.GA19241-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2016-06-23 18:07       ` Stefan Wahren
2016-06-23 18:07         ` Stefan Wahren
2016-06-23 18:07         ` Stefan Wahren
2016-06-25 14:43         ` Greg Kroah-Hartman
2016-06-25 14:43           ` Greg Kroah-Hartman

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=573C7C69.1050301@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=srinivas.kandagatla@linaro.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.