From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753457AbcEROgp (ORCPT ); Wed, 18 May 2016 10:36:45 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:33052 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753413AbcEROgo (ORCPT ); Wed, 18 May 2016 10:36:44 -0400 Subject: Re: [PATCH v3 0/2] nvmem: remove regmap dependency To: Stefan Wahren References: <1462214174-469-1-git-send-email-srinivas.kandagatla@linaro.org> <573C7C69.1050301@i2se.com> Cc: Greg Kroah-Hartman , linux-mediatek@lists.infradead.org, Maxime Ripard , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org From: Srinivas Kandagatla Message-ID: <573C7DF6.6020105@linaro.org> Date: Wed, 18 May 2016 15:36:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <573C7C69.1050301@i2se.com> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18/05/16 15:30, Stefan Wahren wrote: > 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. Thanks Stefan for reporting this, I will send a patch to fix that too. --srini > >