Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1511582 > unrolled thread

Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

Started byLinus Walleij <linus.walleij@linaro.org>
First post2016-10-29 10:30 +0200
Last post2016-10-29 18:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver Linus Walleij <linus.walleij@linaro.org> - 2016-10-29 10:30 +0200
    Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver Michael Scott <michael.scott@linaro.org> - 2016-10-29 18:40 +0200

#1511582 — Re: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver

FromLinus Walleij <linus.walleij@linaro.org>
Date2016-10-29 10:30 +0200
SubjectRe: [PATCH V2] pinctrl: qcom: Add msm8994 pinctrl driver
Message-ID<sxxbA-3Kf-27@gated-at.bofh.it>
On Thu, Oct 27, 2016 at 1:32 AM, Michael Scott <michael.scott@linaro.org> wrote:

> Initial pinctrl driver for QCOM msm8994 platforms.
>
> In order to continue the initial board support for QCOM msm8994/msm8992
> presented in patches from Jeremy McNicoll <jeremymc@redhat.com>, let's put
> a proper pinctrl driver in place.
>
> Currently, the DT for these platforms uses the msm8x74 pinctrl driver to enable
> basic UART.  Beyond the first few pins the rest are different enough to justify
> it's own driver.
>
> Note: This driver is also be used by QCOM's msm8992 platform as it's TLM block
> is the same.
>
> - Initial formatting and style was taken from the msm8x74 pinctrl driver added
>   by Björn Andersson <bjorn.andersson@linaro.org>
> - Data was then adjusted per QCOM MSM8994 documentation for Top Level Multiplexing
> - Bindings documentation was based on qcom,msm8996-pinctrl.txt by
>   Joonwoo Park <joonwoop@codeaurora.org> and then modified for msm8994 content
>
> Signed-off-by: Michael Scott <michael.scott@linaro.org>
> ---
>
> V1 -> V2: fixed missing FUNCTION(nav_pps) and removed 3 odd newlines between blsp_i2c4_groups and cci_timer0_groups

Looks fine to me, just like the other Qcom drivers.

I just want Björn Andersson's ACK before merging, Björn?

Yours,
Linus Walleij

[toc] | [next] | [standalone]


#1511837

FromMichael Scott <michael.scott@linaro.org>
Date2016-10-29 18:40 +0200
Message-ID<sxEPM-vT-25@gated-at.bofh.it>
In reply to#1511582
Resending: The mailing lists bounced due me being silly and replying on 
my phone.

Please reply to this email instead of the last one.

On 10/29/2016 01:27 AM, Linus Walleij wrote:
> On Thu, Oct 27, 2016 at 1:32 AM, Michael Scott <michael.scott@linaro.org> wrote:
>
>> Initial pinctrl driver for QCOM msm8994 platforms.
>>
>> In order to continue the initial board support for QCOM msm8994/msm8992
>> presented in patches from Jeremy McNicoll <jeremymc@redhat.com>, let's put
>> a proper pinctrl driver in place.
>>
>> Currently, the DT for these platforms uses the msm8x74 pinctrl driver to enable
>> basic UART.  Beyond the first few pins the rest are different enough to justify
>> it's own driver.
>>
>> Note: This driver is also be used by QCOM's msm8992 platform as it's TLM block
>> is the same.
>>
>> - Initial formatting and style was taken from the msm8x74 pinctrl driver added
>>    by Björn Andersson <bjorn.andersson@linaro.org>
>> - Data was then adjusted per QCOM MSM8994 documentation for Top Level Multiplexing
>> - Bindings documentation was based on qcom,msm8996-pinctrl.txt by
>>    Joonwoo Park <joonwoop@codeaurora.org> and then modified for msm8994 content
>>
>> Signed-off-by: Michael Scott <michael.scott@linaro.org>
>> ---
>>
>> V1 -> V2: fixed missing FUNCTION(nav_pps) and removed 3 odd newlines between blsp_i2c4_groups and cci_timer0_groups
> Looks fine to me, just like the other Qcom drivers.
>
> I just want Björn Andersson's ACK before merging, Björn?

FYI: I asked Stephen if he could find someone else with tech docs to do 
a data review.  This may or may not happen depending on the internal 
interest level and/or current work load.  It will probably take a week 
or so to get sorted out.

Worst case is no extra set of eyes on the data, and as issues are found 
we can fix them in follow up patches.  The driver works for the current 
msm8994 patches submitted by Jeremy.

Michael Scott

>
> Yours,
> Linus Walleij

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web