linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Varadarajan Narayanan <varada@codeaurora.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
	mturquette@baylibre.com, sboyd@codeaurora.org,
	linus.walleij@linaro.org, andy.gross@linaro.org,
	david.brown@linaro.org, catalin.marinas@arm.com,
	will.deacon@arm.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	absahu@codeaurora.org, sjaganat@codeaurora.org,
	sricharan@codeaurora.org,
	Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
Subject: Re: [PATCH v2 1/5] pinctrl: qcom: Add ipq8074 pinctrl driver
Date: Wed, 17 May 2017 12:33:15 -0700	[thread overview]
Message-ID: <20170517193315.GF12920@tuxbook> (raw)
In-Reply-To: <7afc7191-bcb1-a566-eac5-a4fe1293c773@codeaurora.org>

On Mon 15 May 02:05 PDT 2017, Varadarajan Narayanan wrote:

> On 5/14/2017 9:53 AM, Bjorn Andersson wrote:
> > On Thu 11 May 03:33 PDT 2017, Varadarajan Narayanan wrote:
> > 
> > > On 5/11/2017 4:13 AM, Bjorn Andersson wrote:
> > > > On Thu 04 May 04:53 PDT 2017, Varadarajan Narayanan wrote:
[..]
> > > > > +	msm_mux_qpic_pad4,
> > > > 
> > > > What are qpic_pad and qpic_pad0 through qpic_pad8? Different functions,
> > > > alternative muxings...?
> > > 
> > > This is for the NAND and LCD display. The pins listed are the 9 data pins.
> > > 
> > 
> > Then you can describe them all as "qpic_pad" (or simply "qpic"?). (It's
> > possible to reference a partial group in the DTS, if that's necessary)
> 
> There are two sets of 9 pins, either of which can go to NAND or LCD.
> Will rename qpic_pad as qpic_a and qpic_pad[0-8] as qpic_b.
> Is that ok?
> 

So you have NAND and LCD hardware muxed to either "a" or "b" and then
you mux either "a" or "b" out onto actual pins?

How is this first mux configured?


I think the a/b scheme sounds reasonable, if above is how it works.

Regards,
Bjorn

  parent reply	other threads:[~2017-05-17 19:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 11:53 [PATCH v2 0/5] Add minimal boot support for IPQ8074 Varadarajan Narayanan
2017-05-04 11:53 ` [PATCH v2 1/5] pinctrl: qcom: Add ipq8074 pinctrl driver Varadarajan Narayanan
2017-05-08  5:49   ` Varadarajan Narayanan
2017-05-08 16:38   ` Rob Herring
2017-05-10 22:43   ` Bjorn Andersson
2017-05-11 10:33     ` Varadarajan Narayanan
2017-05-14  4:23       ` Bjorn Andersson
2017-05-15  9:05         ` Varadarajan Narayanan
2017-05-15 11:24           ` Varadarajan Narayanan
2017-05-17 19:47             ` Bjorn Andersson
2017-05-18  8:37               ` Varadarajan Narayanan
2017-05-17 19:33           ` Bjorn Andersson [this message]
2017-05-18  8:39             ` Varadarajan Narayanan
2017-05-20  5:54               ` Bjorn Andersson
2017-05-23  9:26                 ` Linus Walleij
2017-05-04 11:53 ` [PATCH v2 2/5] dt-bindings: qcom: Add IPQ8074 bindings Varadarajan Narayanan
2017-05-08 16:38   ` Rob Herring
2017-05-04 11:53 ` [PATCH v2 3/5] clk: qcom: ipq8074: Add Global Clock Controller support Varadarajan Narayanan
2017-05-08 16:40   ` Rob Herring
2017-05-04 11:54 ` [PATCH v2 4/5] arm64: dts: Add ipq8074 SoC and HK01 board support Varadarajan Narayanan
2017-05-04 11:54 ` [PATCH v2 5/5] arm64: defconfig: Enable QCOM IPQ8074 clock and pinctrl Varadarajan Narayanan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170517193315.GF12920@tuxbook \
    --to=bjorn.andersson@linaro.org \
    --cc=absahu@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mraghava@codeaurora.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=sjaganat@codeaurora.org \
    --cc=sricharan@codeaurora.org \
    --cc=varada@codeaurora.org \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).