Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759596AbaGXPkR (ORCPT ); Thu, 24 Jul 2014 11:40:17 -0400 Received: from mail-oi0-f46.google.com ([209.85.218.46]:52534 "EHLO mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759582AbaGXPkM (ORCPT ); Thu, 24 Jul 2014 11:40:12 -0400 MIME-Version: 1.0 In-Reply-To: <53D04996.2030902@codeaurora.org> References: <1405610748-7583-5-git-send-email-iivanov@mm-sol.com> <1405626085-14069-1-git-send-email-iivanov@mm-sol.com> <20140722214643.GH19700@sonymobile.com> <53D04996.2030902@codeaurora.org> Date: Thu, 24 Jul 2014 17:40:10 +0200 Message-ID: Subject: Re: [PATCH RESEND v2 1/4] pinctrl: Update Qualcomm pm8xxx GPIO parameters definitions From: Linus Walleij To: Stephen Boyd Cc: Bjorn Andersson , "Ivan T. Ivanov" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Mark Brown , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-msm@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 Thu, Jul 24, 2014 at 1:47 AM, Stephen Boyd wrote: >> Please add these constants to the table of valid power-source values and use >> something like I did to translate them to register values - it makes the DT >> much more readable. > > The DT could be similarly readable if we had a bunch of #defines for the > different VIN settings that resolved to the final register value for > that pmic. Something like PM8921_GPIO1_14_VPH, PM8921_GPIO19_36_VPH, > etc. There would be a lot of them, but then the driver could be really > simple and just jam whatever value is in the DT into the register > without having to bounce through a mapping table in software to figure > out the register value. If we did this for the functions also then I > believe we achieve readability without requiring a bunch of drivers for > each and every single pmic? Not sure but it sounds like you want to make the device tree a jam table, (know about individual register offsets, sequences etc). That has been throrougly NACKed in the past, because DT is not Open Firmware. The exception is pinctrl-single which is restricted to single register per pin use cases and is still a point of contention... Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/