[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ffc9474-0a05-44d8-0cc0-24a065443b18@quicinc.com>
Date: Wed, 10 May 2023 20:00:50 +0530
From: Rohit Agarwal <quic_rohiagar@...cinc.com>
To: <andy.shevchenko@...il.com>
CC: <agross@...nel.org>, <andersson@...nel.org>,
<konrad.dybcio@...aro.org>, <linus.walleij@...aro.org>,
<robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<richardcochran@...il.com>, <manivannan.sadhasivam@...aro.org>,
<linux-arm-msm@...r.kernel.org>, <linux-gpio@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH v6 4/4] pinctrl: qcom: Add SDX75 pincontrol driver
On 5/10/2023 7:49 PM, andy.shevchenko@...il.com wrote:
> Wed, May 10, 2023 at 05:08:45PM +0530, Rohit Agarwal kirjoitti:
>> Add initial Qualcomm SDX75 pinctrl driver to support pin configuration
>> with pinctrl framework for SDX75 SoC.
>> While at it, reordering the SDX65 entry.
> ...
>
>> +#define FUNCTION(n) \
>> + [msm_mux_##n] = { \
>> + .func = PINCTRL_PINFUNCTION(#n, \
>> + n##_groups, \
>> + ARRAY_SIZE(n##_groups)) \
>> + }
> But don't you now have MSM_PIN_FUNCTION() macro?
So Sorry, a mistake from my end. Will immediately update.
Thanks for reviewing.
Rohit.
>
Powered by blists - more mailing lists