From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752669AbbFENjO (ORCPT ); Fri, 5 Jun 2015 09:39:14 -0400 Received: from hqemgate15.nvidia.com ([216.228.121.64]:10413 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751603AbbFENjL (ORCPT ); Fri, 5 Jun 2015 09:39:11 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Fri, 05 Jun 2015 06:36:36 -0700 Message-ID: <5571A5E3.3070700@nvidia.com> Date: Fri, 5 Jun 2015 19:06:35 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Mark Brown CC: , , , , Subject: Re: [PATCH 1/2] regulator: core: add support to get VSEL register from hw driver References: <1432737621-27590-1-git-send-email-ldewangan@nvidia.com> <20150528135245.GU21577@sirena.org.uk> <5567FE68.5070006@nvidia.com> <20150529094941.GL21577@sirena.org.uk> In-Reply-To: <20150529094941.GL21577@sirena.org.uk> X-Originating-IP: [10.19.65.30] X-ClientProxiedBy: DRUKMAIL102.nvidia.com (10.25.59.20) To bgmail102.nvidia.com (10.25.59.11) Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 29 May 2015 03:19 PM, Mark Brown wrote: > The problem will be there when external controller use the DVS pin for DVFS > and need two register address here. In this case, I think external > controller need to get information from different mechanism rather than via > regulator driver to avoid complication on regulator driver/framework. > Probably, it's definitely getting complicated (though in this case where > we only need one register we ought to be more able to manage it, not > that I have bright ideas right now). > Hi Mark, Are you accepting this patch? I am not much clear on the conclusion and hence my question is. Is anything pending from me to provide any information? I have some more patches pending on MAX8973 for supporting MAX77621 device and if this series is not fine, I like to go on next set of patches while we discussing this need. Thanks, Laxman