mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krishna Kurapati <quic_kriskura@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Bjorn Andersson <quic_bjorande@quicinc.com>,
	Wesley Cheng <quic_wcheng@quicinc.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	"Tingwei Zhang" <quic_tingweiz@quicinc.com>,
	Conor Dooley <conor+dt@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-phy@lists.infradead.org>, <quic_ppratap@quicinc.com>,
	<quic_jackp@quicinc.com>
Subject: Re: [PATCH v2 5/5] phy: qcom: qmp-usbc: Add qmp configuration for QCS615
Date: Fri, 18 Oct 2024 15:53:22 +0530	[thread overview]
Message-ID: <479f7aa2-0401-40d5-8e2f-d7512aeab0c0@quicinc.com> (raw)
In-Reply-To: <l4wpt5qin3ezkowf3puvodrm5wjsptd4a32f4qrzcuuquo6kq6@j2orv5z5quln>



On 10/18/2024 3:41 PM, Dmitry Baryshkov wrote:
> On Fri, Oct 18, 2024 at 05:01:48PM +0800, Tingwei Zhang wrote:
>> On 10/18/2024 4:06 PM, Dmitry Baryshkov wrote:
>>> On Fri, 18 Oct 2024 at 10:48, Tingwei Zhang <quic_tingweiz@quicinc.com> wrote:
>>>>
>>>> On 10/18/2024 2:27 AM, Dmitry Baryshkov wrote:
>>>>> On Thu, 17 Oct 2024 at 16:07, Krishna Kurapati
>>>>> <quic_kriskura@quicinc.com> wrote:
>>>>>>
>>>>>> Provide PHY configuration for the USB QMP PHY for QCS615 Platform.
>>>>>>
>>>>>> Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
>>>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>>
>>>>> After checking platform details,
>>>>>
>>>>> Unreviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>>
>>>>> Please perform global s/QCS615/SM6150/ and s/qcs615/sm6150/
>>>>
>>>> QCS615 and SM6150 are different variants of the same SoC. QCS615 is an
>>>> IoT variant, while SM6150 is a mobile variant. We are currently adding
>>>> QCS615 SoC support to the upstream Kernel, as it is in an active
>>>> development stage and we anticipate many products based on this SoC. On
>>>> the other hand, the SM6150 is an older mobile platform that is unlikely
>>>> to be used in new designs. For a product introduction of the QCS615,
>>>> please refer to
>>>> https://docs.qualcomm.com/bundle/publicresource/87-83838-1_REV_A_Qualcomm_IQ6_Series_Product_Brief.pdf
>>>
>>> Yes, I guessed so. It would have been nice if it was documented this
>>> way from the beginning.
>>>
>>> Please note that we usually get support for the mobile SoC first. So
>>> in most of the cases devices use mobile compatible even for IoT
>>> platforms, see qrb5165, qrb4210, qcm6490 and other similar platforms.
>>> I simply asked to follow the established pattern.
>>
>> Yes, we start from mobile variant for most of the platforms. There are some
>> exceptions like sc7180 and sc7280 which we started from compute variant
>> since they are widely used by compute platform on upstream Kernel. I think
>> we have similar case here. QCS615 will be widely used by IOT products on
>> upstream Kernel. We should have clarified this from beginning so there's no
>> ambiguity.
> 
> After offline discussion with Krzysztof, I'll lift my objection, so
> still Reviewed-by.
> 

Thanks Dmitry.

Can you help review patch-4 of the series. I made the changes you 
suggested on v1 (uppercase to lowercase and removing un-necessary re-inits).

Regards,
Krishna,

  reply	other threads:[~2024-10-18 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 13:06 [PATCH v2 0/5] Add support for primary USB controller on QCS615 Krishna Kurapati
2024-10-17 13:06 ` [PATCH v2 1/5] dt-bindings: usb: qcom,dwc3: Add QCS615 to USB DWC3 bindings Krishna Kurapati
2024-10-17 13:06 ` [PATCH v2 2/5] dt-bindings: phy: qcom,qusb2: Add bindings for QCS615 Krishna Kurapati
2024-10-17 13:06 ` [PATCH v2 3/5] dt-bindings: phy: qcom,msm8998-qmp-usb3-phy: Add support " Krishna Kurapati
2024-10-17 13:07 ` [PATCH v2 4/5] phy: qcom-qusb2: " Krishna Kurapati
2024-10-18 10:48   ` Dmitry Baryshkov
2024-10-17 13:07 ` [PATCH v2 5/5] phy: qcom: qmp-usbc: Add qmp configuration " Krishna Kurapati
2024-10-17 18:27   ` Dmitry Baryshkov
2024-10-18  7:48     ` Tingwei Zhang
2024-10-18  8:06       ` Dmitry Baryshkov
2024-10-18  9:01         ` Tingwei Zhang
2024-10-18 10:11           ` Dmitry Baryshkov
2024-10-18 10:23             ` Krishna Kurapati [this message]
2024-10-18 10:49               ` Dmitry Baryshkov

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=479f7aa2-0401-40d5-8e2f-d7512aeab0c0@quicinc.com \
    --to=quic_kriskura@quicinc.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_bjorande@quicinc.com \
    --cc=quic_jackp@quicinc.com \
    --cc=quic_ppratap@quicinc.com \
    --cc=quic_tingweiz@quicinc.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®