From: Jeremy McNicoll <jmcnicol@redhat.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Jeremy McNicoll <jeremymc@redhat.com>
Cc: linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org,
andy.gross@linaro.org, sboyd@codeaurora.org, arnd@arndb.de,
mark.rutland@arm.com, michael.scott@linaro.org
Subject: Re: [RFC V4 PATCH 6/6] arm64: configs: enable configs for msm899(2/4) basic support
Date: Tue, 25 Oct 2016 01:07:06 -0700 [thread overview]
Message-ID: <20161025080706.GD21964@mini-rhel.redhat.com> (raw)
In-Reply-To: <ba4e8128-40c1-e2ff-8eda-130cbb62e71e@redhat.com>
On Fri, Oct 21, 2016 at 03:32:08PM -0700, Jeremy McNicoll wrote:
> On 2016-10-21 11:27 AM, Bjorn Andersson wrote:
> >On Fri 21 Oct 04:11 PDT 2016, Jeremy McNicoll wrote:
> >
> >>From: Jeremy McNicoll <jmcnicol@redhat.com>
> >>
> >>Given the mimimal hardware support for msm899(2/4) currently.
> >>A few config options are needed to allow for continued
> >>development and booting.
> >>
> >>The following are needed for continued development and
> >>booting:
> >> -8x74 pinctrl for serial support
> >
> >I don't have the datasheet for 899[24], but I don't think this is a good
> >idea. We need a 899[24] pinctrl driver for this.
> >
>
> Based on the downstream code, for serial it was sufficient.
>
> There is a 8994 pinctrl driver on its away.
>
Here is a link to the 8994 pinctrl needed for 899(2/4).
https://patches.linaro.org/patch/78750/
-jeremy
prev parent reply other threads:[~2016-10-25 8:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:11 [RFC V4 PATCH 0/6] msm8992/msm8994: Google Nexus 5X/6P initial board support Jeremy McNicoll
2016-10-21 11:11 ` [RFC V4 PATCH 5/6] arm64: dts: msm8994 SoC and Huawei Angler (Nexus 6P) support Jeremy McNicoll
2016-10-21 18:25 ` Bjorn Andersson
2016-10-25 8:00 ` Jeremy McNicoll
[not found] ` <1477048273-32451-1-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-21 11:11 ` [RFC V4 PATCH 1/6] arm64: dts: msm8992 SoC and LG Bullhead (Nexus 5X) support Jeremy McNicoll
2016-10-21 18:20 ` Bjorn Andersson
2016-10-25 8:15 ` Jeremy McNicoll
[not found] ` <1477048273-32451-2-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-21 19:21 ` Stephen Boyd
[not found] ` <20161021192147.GM26139-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-10-25 9:40 ` Jeremy McNicoll
2016-10-25 10:41 ` Jeremy McNicoll
2016-10-21 11:11 ` [RFC V4 PATCH 2/6] dt-bindings: qcom: clocks: Add msm8994 clock bindings Jeremy McNicoll
2016-10-21 11:11 ` [RFC V4 PATCH 3/6] msm8994 clocks: global clock support for msm8994 SOC Jeremy McNicoll
2016-10-21 11:11 ` [RFC V4 PATCH 4/6] dt-bindings: qcom: Add msm899(2/4) bindings Jeremy McNicoll
2016-10-21 11:11 ` [RFC V4 PATCH 6/6] arm64: configs: enable configs for msm899(2/4) basic support Jeremy McNicoll
[not found] ` <1477048273-32451-7-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-21 18:27 ` Bjorn Andersson
2016-10-21 22:32 ` Jeremy McNicoll
2016-10-25 8:07 ` Jeremy McNicoll [this message]
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=20161025080706.GD21964@mini-rhel.redhat.com \
--to=jmcnicol@redhat.com \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jeremymc@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.scott@linaro.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.