From mboxrd@z Thu Jan 1 00:00:00 1970 From: linus.walleij@linaro.org (Linus Walleij) Date: Tue, 23 May 2017 11:26:24 +0200 Subject: [PATCH v2 1/5] pinctrl: qcom: Add ipq8074 pinctrl driver In-Reply-To: <20170520055430.GU12920@tuxbook> References: <1493898841-20583-1-git-send-email-varada@codeaurora.org> <1493898841-20583-2-git-send-email-varada@codeaurora.org> <20170510224355.GE45273@Bjorns-MacBook-Pro-2.local> <1f4c9974-f6a4-bee7-4f37-ad8795e442a3@codeaurora.org> <20170514042307.GE69278@Bjorns-MacBook-Pro-2.local> <7afc7191-bcb1-a566-eac5-a4fe1293c773@codeaurora.org> <20170517193315.GF12920@tuxbook> <20170520055430.GU12920@tuxbook> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sat, May 20, 2017 at 7:54 AM, Bjorn Andersson wrote: > On Thu 18 May 01:39 PDT 2017, Varadarajan Narayanan wrote: >> There are 18 pins. 15 pins are common between LCD and NAND. The QPIC >> controller arbitrates between LCD and NAND. Of the remaining 4, 2 are for >> NAND and 2 are for LCD exclusively. We plan to group the qpic pins into 3 >> groups namely, qpic_common, qpic_nand and qpic_lcd. Is that ok? >> > > If you consider that you are defining the available functions for this > pinmuxer and then define the sets of pins exposing these available > functions it does make sense to just name it "qpic". > > I think that naming them _common, _lcd and _nand is just adding > confusion when it comes to writing the dts files. > > @Linus, do you have a different preference here? No I pretty much trust the driver maintainer to know this best. Yours, Linus Walleij