From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Andersson Subject: Re: [PATCH 0/4] New Qualcomm PMIC pin controller drivers Date: Wed, 9 Jul 2014 07:02:48 -0700 Message-ID: References: <1404745893-6379-1-git-send-email-iivanov@mm-sol.com> <1404904380.16296.17.camel@iivanov-dev> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-ob0-f171.google.com ([209.85.214.171]:45544 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755124AbaGIOCs convert rfc822-to-8bit (ORCPT ); Wed, 9 Jul 2014 10:02:48 -0400 Received: by mail-ob0-f171.google.com with SMTP id wm4so2148436obc.30 for ; Wed, 09 Jul 2014 07:02:48 -0700 (PDT) In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Linus Walleij Cc: "Ivan T. Ivanov" , Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Grant Likely , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" On Wed, Jul 9, 2014 at 4:43 AM, Linus Walleij wrote: > On Wed, Jul 9, 2014 at 1:13 PM, Ivan T. Ivanov w= rote: >> On Wed, 2014-07-09 at 11:43 +0200, Linus Walleij wrote: >>> On Mon, Jul 7, 2014 at 5:11 PM, Ivan T. Ivanov = wrote: >>> Oh, I just spent some 45 minutes reviewing an 8xxx pinctrl driver f= rom >>> Bj=C3=B6rn Andersson >>> that *seems* to be doing exactly the same thing. >>> Sorry for not getting comments out on Ivan's patches before you got her= e. >>> Now I have two drivers from people outside Qualcomm :-) >>> :) >>> Some of my review comments on Bj=C3=B6rn's driver (like using SI un= its with the pin >>> config) are actually adressed in this patch set. The idea to split = in subdrivers >>> per-ASIC may be good? I don't really know. >>> >>> Can you two guys *PLEASE* join efforts and combine your drivers int= o one? >> The drivers can't be merged; the hardware is more or less identical, but the register map is completely different. However, the device tree bindings are a different thing; as the properties used to describe the hardware doesn't relate to how we communicate with it I think we should be able to (and therefor should) use the same documentation for the two (rather 7) chips. >> Not sure. Bj=C3=B6rn patches cover older PMIC chips, if not mistaken= , mine >> cover PMIC's used with APQ8074 and onward [1]. Main difference is >> the bus which connects them to SoC, interrupts handling, runtime >> pin type detection and register map. > Correct Ivan; we do however share the same issues related to how to do interrupt handling, units for properties and how to split/reuse between gpio and mpp. Also we have solved the pins vs groups vs functions slightly different, that should all be aligned I think. > Oh OK... then atleast there is something wrong with the naming of > Bj=C3=B6rns patches as they are 8xxx and your chips are also named > 8xxx ... > So, the pm8xxx series of drivers refer to pm8018, pm8038, pm8058, pm8917 and pm8921 which are used in platforms in 8660, 8960 and 8064 (among others). The driver that Ivan posted is for the pm8841 and pm8941; these are using spmi instead of ssbi which gives a larger addressing space and allows for a less dense register map, so all the plumbing in those drivers will be different. The suggestion is to call the "new gen stuff" qpnp instead, but to me that's just a setup for hitting the same problem in a few years... Nontheless, the hardware guys have painted us into a corner where pm8xxx refer to a series of very similar pmics and pm8x41 is not one of those. > Anyway I will create a patch to move the current msm driver down > to a folder named "qcom" and we can atleast collect these drivers > in a single place since the chipsets are related, OK? > +1 > Then I guess even if the chips are totally unrelated it'd be interest= ing > to have you two guys cross-review each other's drivers so the behavio= ur > is consistent across qualcomm platforms. > I hope we can meet somewhere in between, so that we and other developers will be able to recognize the common element and structures later on. Again, sorry for not finding the time to preempt you on that. Regards, Bjorn