Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <8a4ccbc6-cf81-1939-40f6-4796550fc646@quicinc.com>
Date:   Tue, 9 Aug 2022 11:02:21 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.0
Subject: Re: [PATCH V3 2/2] arm64: dts: qcom: sc7280: Update lpassaudio clock
 controller for resets
Content-Language: en-US
To:     Stephen Boyd <swboyd@chromium.org>,
        Bjorn Andersson <bjorn.andersson@linaro.org>,
        Rob Herring <robh+dt@kernel.org>
CC:     Douglas Anderson <dianders@chromium.org>,
        Andy Gross <agross@kernel.org>, <devicetree@vger.kernel.org>,
        <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <quic_tdas@quicinc.com>
References: <1658316144-16520-1-git-send-email-quic_c_skakit@quicinc.com>
 <1658316144-16520-3-git-send-email-quic_c_skakit@quicinc.com>
 <CAE-0n53wdhH2P729KDDbghScCcU=4-sFmxVugyJgxmGeFs4mgw@mail.gmail.com>
 <e28ef7e2-c23a-f87b-09b2-958f2212c30e@quicinc.com>
 <CAE-0n50qou6zy6E=cDafMi6RknMjtVgDiBnbeVE+tNTj-JLshw@mail.gmail.com>
From:   "Satya Priya Kakitapalli (Temp)" <quic_c_skakit@quicinc.com>
In-Reply-To: <CAE-0n50qou6zy6E=cDafMi6RknMjtVgDiBnbeVE+tNTj-JLshw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 8/9/2022 5:43 AM, Stephen Boyd wrote:
> Quoting Satya Priya Kakitapalli (Temp) (2022-07-26 22:51:08)
>> On 7/27/2022 6:52 AM, Stephen Boyd wrote:
>>> Quoting Satya Priya (2022-07-20 04:22:24)
>>>> From: Taniya Das <quic_tdas@quicinc.com>
>>>>
>>>> The lpass audio supports TX/RX/WSA block resets. Also to keep
>>>> consistency update lpasscore to lpass_core.
>>> Consistency with what?
>>
>> Hi Stephen,
>>
>>
>> We got a comment to change this on previous posts, to keep consistency
>> with the other nodes like lpass_aon etc
> Can you make that change in a different patch? Then the focus can be on
> what the patch subject is about. You're not changing the same lines,
> right?


No, I will move this change to separate patch.