From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752282AbcKHPqS (ORCPT ); Tue, 8 Nov 2016 10:46:18 -0500 Received: from mail-qk0-f179.google.com ([209.85.220.179]:33314 "EHLO mail-qk0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752014AbcKHPqN (ORCPT ); Tue, 8 Nov 2016 10:46:13 -0500 MIME-Version: 1.0 In-Reply-To: <5821D49E.2070308@nvidia.com> References: <1478077742-25437-1-git-send-email-ldewangan@nvidia.com> <1478077742-25437-3-git-send-email-ldewangan@nvidia.com> <58201401.8050805@nvidia.com> <5821A6D3.7010000@nvidia.com> <5821D49E.2070308@nvidia.com> From: Linus Walleij Date: Tue, 8 Nov 2016 16:46:11 +0100 Message-ID: Subject: Re: [PATCH 2/2] pinctrl: tegra: Add driver to configure voltage and power of io pads To: Laxman Dewangan Cc: "thierry.reding@gmail.com" , Stephen Warren , Rob Herring , Mark Rutland , Jon Hunter , Masahiro Yamada , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 8, 2016 at 2:35 PM, Laxman Dewangan wrote: > There is two types of configuration in given platform, the IO voltage does > not get change (fixed in given platform) and in some of cases, get change > dynamically like SDIO3.0 where the voltage switches to 3.3V and 1.8V. > > Yes, it can be integrated with the regulator handle and then it can call the > required configurations through notifier and regulator_get_voltage(). > But I think it is too much complex for the static configurations. This > mandate also to populate the regulator handle and all power tree. > > The simple way for static configuration (case where voltage does not get > change), just take the power tree IO voltage from DT and configure the IO > pad control register. > > For dynamic case, there is some sequence need to be followed based on > voltage direction change (towards lower or towards higher) for the voltage > change and the IO pad voltage configuration and it is simple to do it from > client driver. The devicetree should describe the platform. Adding this custom attribute does not describe the platform very well since the dependency to the corresponding regulator is hidden. The point of device tree is not as much to make things simple as to describe the world properly. So to me it is simple: use regulators and phandles. It might require a bit of upfront coding but the result will look much nicer. Yours, Linus Walleij