From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] usb: typec: Add support for Parade PS8830 Type-C Retimer
Date: Wed, 23 Oct 2024 18:10:58 +0200 [thread overview]
Message-ID: <ZxkgEjptmmHpQpfB@hovoldconsulting.com> (raw)
In-Reply-To: <ZxiuFRFnZFlcdMPs@linaro.org>
On Wed, Oct 23, 2024 at 11:04:37AM +0300, Abel Vesa wrote:
> On 24-10-23 09:52:19, Johan Hovold wrote:
> > I'm talking about an I/O pin here, you must generally not drive those
> > high before powering on the IC.
> >
> > And AFAIU the same applies to clocks even though the risk of damage
> > there is lower.
>
> As I stated before, enabling (or rather preparing, from kernel's point
> of view) will definitely glitch due to PLL switcing (unless the mux is
> glitchless from design). And there is literally no risk of enabling or
> keeping a clock enabled even if the consumer is powered off.
That's a separate discussion from whether you should supply clocks to an
unpowered IC, and you can get around that by making sure the IC is held
in reset until the clock is stable.
What does the datasheet say about the XTALO_REFCLK_IN pin? What's the
max voltage specified as?
And since the machine we are currently working on do not using a crystal
oscillator here, do you need to configure the device to use a clock
instead somehow?
Is there any mention of the refclk in the power-on sequence?
Johan
next prev parent reply other threads:[~2024-10-23 16:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 13:57 [PATCH v2 0/2] usb: typec: Add new driver for Parade PS8830 Type-C Retimer Abel Vesa
2024-10-04 13:57 ` [PATCH v2 1/2] dt-bindings: usb: Add Parade PS8830 Type-C retimer bindings Abel Vesa
2024-10-05 17:36 ` Rob Herring
2024-10-06 15:25 ` Dmitry Baryshkov
2024-10-06 15:28 ` Dmitry Baryshkov
2024-10-22 7:02 ` Abel Vesa
2024-10-06 15:30 ` Dmitry Baryshkov
2024-10-15 12:48 ` Johan Hovold
2024-10-04 13:57 ` [PATCH v2 2/2] usb: typec: Add support for Parade PS8830 Type-C Retimer Abel Vesa
2024-10-06 15:40 ` Dmitry Baryshkov
2024-10-18 18:11 ` Abel Vesa
2024-10-15 13:03 ` Johan Hovold
2024-10-22 9:01 ` Abel Vesa
2024-10-23 7:04 ` Johan Hovold
2024-10-23 7:32 ` Abel Vesa
2024-10-23 7:52 ` Johan Hovold
2024-10-23 8:04 ` Abel Vesa
2024-10-23 16:10 ` Johan Hovold [this message]
2024-10-22 7:41 ` Christophe JAILLET
2024-10-22 8:29 ` Abel Vesa
2024-10-15 12:41 ` [PATCH v2 0/2] usb: typec: Add new driver " Johan Hovold
2024-10-15 13:03 ` Abel Vesa
2024-10-15 19:10 ` Konrad Dybcio
2024-10-17 6:00 ` Johan Hovold
2024-10-17 8:25 ` Abel Vesa
2024-10-22 7:25 ` Johan Hovold
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=ZxkgEjptmmHpQpfB@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=robh@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