From: Baruch Siach <baruch@tkos.co.il>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Robert Marko <robimarko@gmail.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:GENERIC PHY FRAMEWORK" <linux-phy@lists.infradead.org>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: ipq8074 USB PHY
Date: Thu, 29 Sep 2022 19:52:14 +0300 [thread overview]
Message-ID: <87k05mm875.fsf@tarshish> (raw)
In-Reply-To: <75bb4a68-f47d-1de1-a900-789e365be41e@linaro.org>
Hi Dmitry,
On Thu, Sep 29 2022, Dmitry Baryshkov wrote:
> We have been looking onto the QMP PHY programming in the upstream kernels. I
> noticed that the ipq8074_usb3phy_cfg uses usb3phy_regs_layout for the regs
> layout, however the Qualcomm's kernel ([1]) defines offsets which correspond
> to qmp_v3_usb3phy_regs_layout. As you seem to be working with this platform,
> could you please doublecheck which of layouts is correct? Thank you.
>
> [1]
> https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/tree/arch/arm64/boot/dts/qcom/qcom-ipq807x-soc.dtsi?h=NHSS.QSDK.9.0.2&id=894e56082ca89638c68b7cee039ac1b2a6cb4863#n1237
The platform I have access to is IPQ6018 based. Only USB2 signals are
connected on the board. I can't help with testing of USB3 PHY
initialization. Sorry.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2022-09-29 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 11:26 ipq8074 USB PHY Dmitry Baryshkov
2022-09-29 11:51 ` Robert Marko
2022-09-29 16:52 ` Baruch Siach [this message]
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=87k05mm875.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robimarko@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).