Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1410936 > unrolled thread
| Started by | Stefan Wahren <stefan.wahren@i2se.com> |
|---|---|
| First post | 2016-06-01 10:30 +0200 |
| Last post | 2016-06-01 20:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v3 0/2] nvmem: remove regmap dependency Stefan Wahren <stefan.wahren@i2se.com> - 2016-06-01 10:30 +0200
Re: [PATCH v3 0/2] nvmem: remove regmap dependency Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-06-01 20:00 +0200
| From | Stefan Wahren <stefan.wahren@i2se.com> |
|---|---|
| Date | 2016-06-01 10:30 +0200 |
| Subject | Re: [PATCH v3 0/2] nvmem: remove regmap dependency |
| Message-ID | <rF9Hj-60K-13@gated-at.bofh.it> |
Hi Greg,
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.
>
> This patchset converts the nvmem core and nvmem provider drivers to
> use the new callbacks. Tested this patchset on qfprom and at24 drivers.
> Other driver are only compile tested, any testing on them would be great.
>
> Most of the patches have been applied to char-misc tree, these are the
> two patches which had some outstanding comments on mxs nvmemprovider,
> which are now fixed.
>
> Changes since v2:
> - Fixed the mxs size and dt data pointer spotted by Stefan and Fabio
>
> Changes since v1:
> - rebased mtk-efuse on top of char-misc
> - addressed concerns raised by Stefan Wahren.
>
> [1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1130026.html
>
> Thanks,
> srini
>
> Srinivas Kandagatla (2):
> nvmem: mtk-efuse: remove nvmem regmap dependency
> nvmem: mxs-ocotp: remove nvmem regmap dependency
>
> drivers/nvmem/Kconfig | 1 -
> drivers/nvmem/mtk-efuse.c | 47 ++++++++++++++++++---------
> drivers/nvmem/mxs-ocotp.c | 83 +++++++++++++----------------------------------
> 3 files changed, 54 insertions(+), 77 deletions(-)
>
any objections about this series or is it still in queue?
Stefan
[toc] | [next] | [standalone]
| From | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| Date | 2016-06-01 20:00 +0200 |
| Message-ID | <rFiAW-3aE-35@gated-at.bofh.it> |
| In reply to | #1410936 |
On Wed, Jun 01, 2016 at 10:27:49AM +0200, Stefan Wahren wrote:
> Hi Greg,
>
> 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.
> >
> > This patchset converts the nvmem core and nvmem provider drivers to
> > use the new callbacks. Tested this patchset on qfprom and at24 drivers.
> > Other driver are only compile tested, any testing on them would be great.
> >
> > Most of the patches have been applied to char-misc tree, these are the
> > two patches which had some outstanding comments on mxs nvmemprovider,
> > which are now fixed.
> >
> > Changes since v2:
> > - Fixed the mxs size and dt data pointer spotted by Stefan and Fabio
> >
> > Changes since v1:
> > - rebased mtk-efuse on top of char-misc
> > - addressed concerns raised by Stefan Wahren.
> >
> > [1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1130026.html
> >
> > Thanks,
> > srini
> >
> > Srinivas Kandagatla (2):
> > nvmem: mtk-efuse: remove nvmem regmap dependency
> > nvmem: mxs-ocotp: remove nvmem regmap dependency
> >
> > drivers/nvmem/Kconfig | 1 -
> > drivers/nvmem/mtk-efuse.c | 47 ++++++++++++++++++---------
> > drivers/nvmem/mxs-ocotp.c | 83 +++++++++++++----------------------------------
> > 3 files changed, 54 insertions(+), 77 deletions(-)
> >
>
> any objections about this series or is it still in queue?
still in my queue...
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web