[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y853iEBf1e7uh/wX@hovoldconsulting.com>
Date: Mon, 23 Jan 2023 13:03:20 +0100
From: Johan Hovold <johan@...nel.org>
To: Luca Weiss <luca.weiss@...rphone.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Vinod Koul <vkoul@...nel.org>, linux-arm-msm@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Kishon Vijay Abraham I <kishon@...nel.org>,
linux-phy@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/3] phy: qcom-qmp-combo: Add config for SM6350
On Mon, Jan 23, 2023 at 12:22:32PM +0100, Luca Weiss wrote:
> On Mon Jan 23, 2023 at 12:15 PM CET, Dmitry Baryshkov wrote:
> > There are two SERDES regions. One used by USB part of the PHY (at
> > 0x1000) and another SERDES region used for DP (at 0x2000). As Johan
> > described below, vendor kernel handles the DP regions in the DP driver.
> > Possibly this caused a confusion on your side.
>
> Ack, I think I got it now. I also see the registers used downstream
> now, e.g.:
>
> techpack/display/pll/dp_pll_10nm_util.c:#define QSERDES_COM_LOCK_CMP2_MODE0 0x009C
>
> So now .dp_serdes should be 0x2000. Do I need to change anything else
> also? I think not?
You also need to add new dp_tx/rx pointers to the offset struct and use
those in favour of the current ones if set. I think we hashed that bit
out in one of the previous versions of this patch.
Johan
Powered by blists - more mailing lists