Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 14 Jan 2021 19:16:21 -0800 you wrote:
> There's currently a comment in the code saying function 0 is GPIO.
> Instead of hardcoding it, let's add a member where an SoC can specify
> it. No known SoCs use a number other than 0, but this just makes the
> code clearer. NOTE: no SoC code needs to be updated since we can rely
> on zero-initialization.
>
> Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx>
> Reviewed-by: Stephen Boyd <swboyd@xxxxxxxxxxxx>
> Reviewed-by: Maulik Shah <mkshah@xxxxxxxxxxxxxx>
> Tested-by: Maulik Shah <mkshah@xxxxxxxxxxxxxx>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx>
>
> [...]
Here is the summary with links:
- [v7,1/4] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0
https://git.kernel.org/qcom/c/a82e537807d5
- [v7,2/4] pinctrl: qcom: No need to read-modify-write the interrupt status
https://git.kernel.org/qcom/c/4079d35fa4fc
- [v7,3/4] pinctrl: qcom: Properly clear "intr_ack_high" interrupts when unmasking
https://git.kernel.org/qcom/c/a95881d6aa2c
- [v7,4/4] pinctrl: qcom: Don't clear pending interrupts when enabling
https://git.kernel.org/qcom/c/cf9d052aa600
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
