From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> To: Johan Hovold <johan+linaro@kernel.org>, Vinod Koul <vkoul@kernel.org> Cc: Andy Gross <agross@kernel.org>, Bjorn Andersson <bjorn.andersson@linaro.org>, Kishon Vijay Abraham I <kishon@ti.com>, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] phy: qcom-qmp: clean up v4 and v5 define order Date: Thu, 23 Jun 2022 14:49:39 +0300 [thread overview] Message-ID: <80da3045-5351-5d21-ffb2-e514e0b25961@linaro.org> (raw) In-Reply-To: <20220609120338.4080-2-johan+linaro@kernel.org> On 09/06/2022 15:03, Johan Hovold wrote: > Clean up the QMP v4 and v5 defines by moving a few entries that were out > of order. > > Signed-off-by: Johan Hovold <johan+linaro@kernel.org> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > --- > drivers/phy/qualcomm/phy-qcom-qmp.h | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.h b/drivers/phy/qualcomm/phy-qcom-qmp.h > index eb5705d1e32c..626be0ccede2 100644 > --- a/drivers/phy/qualcomm/phy-qcom-qmp.h > +++ b/drivers/phy/qualcomm/phy-qcom-qmp.h > @@ -577,8 +577,8 @@ > #define QSERDES_V4_COM_LOCK_CMP1_MODE0 0x0ac > #define QSERDES_V4_COM_LOCK_CMP2_MODE0 0x0b0 > #define QSERDES_V4_COM_LOCK_CMP1_MODE1 0x0b4 > -#define QSERDES_V4_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V4_COM_LOCK_CMP2_MODE1 0x0b8 > +#define QSERDES_V4_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V4_COM_DEC_START_MODE1 0x0c4 > #define QSERDES_V4_COM_DIV_FRAC_START1_MODE0 0x0cc > #define QSERDES_V4_COM_DIV_FRAC_START2_MODE0 0x0d0 > @@ -1106,8 +1106,8 @@ > #define QSERDES_V5_COM_LOCK_CMP1_MODE0 0x0ac > #define QSERDES_V5_COM_LOCK_CMP2_MODE0 0x0b0 > #define QSERDES_V5_COM_LOCK_CMP1_MODE1 0x0b4 > -#define QSERDES_V5_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V5_COM_LOCK_CMP2_MODE1 0x0b8 > +#define QSERDES_V5_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V5_COM_DEC_START_MODE1 0x0c4 > #define QSERDES_V5_COM_DIV_FRAC_START1_MODE0 0x0cc > #define QSERDES_V5_COM_DIV_FRAC_START2_MODE0 0x0d0 > @@ -1134,8 +1134,8 @@ > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE1_MODE0 0x1ac > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE2_MODE0 0x1b0 > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE1_MODE1 0x1b4 > -#define QSERDES_V5_COM_BIN_VCOCAL_HSCLK_SEL 0x1bc > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE2_MODE1 0x1b8 > +#define QSERDES_V5_COM_BIN_VCOCAL_HSCLK_SEL 0x1bc > > /* Only for QMP V5 PHY - TX registers */ > #define QSERDES_V5_TX_RES_CODE_LANE_TX 0x34 -- With best wishes Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> To: Johan Hovold <johan+linaro@kernel.org>, Vinod Koul <vkoul@kernel.org> Cc: Andy Gross <agross@kernel.org>, Bjorn Andersson <bjorn.andersson@linaro.org>, Kishon Vijay Abraham I <kishon@ti.com>, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] phy: qcom-qmp: clean up v4 and v5 define order Date: Thu, 23 Jun 2022 14:49:39 +0300 [thread overview] Message-ID: <80da3045-5351-5d21-ffb2-e514e0b25961@linaro.org> (raw) In-Reply-To: <20220609120338.4080-2-johan+linaro@kernel.org> On 09/06/2022 15:03, Johan Hovold wrote: > Clean up the QMP v4 and v5 defines by moving a few entries that were out > of order. > > Signed-off-by: Johan Hovold <johan+linaro@kernel.org> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > --- > drivers/phy/qualcomm/phy-qcom-qmp.h | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.h b/drivers/phy/qualcomm/phy-qcom-qmp.h > index eb5705d1e32c..626be0ccede2 100644 > --- a/drivers/phy/qualcomm/phy-qcom-qmp.h > +++ b/drivers/phy/qualcomm/phy-qcom-qmp.h > @@ -577,8 +577,8 @@ > #define QSERDES_V4_COM_LOCK_CMP1_MODE0 0x0ac > #define QSERDES_V4_COM_LOCK_CMP2_MODE0 0x0b0 > #define QSERDES_V4_COM_LOCK_CMP1_MODE1 0x0b4 > -#define QSERDES_V4_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V4_COM_LOCK_CMP2_MODE1 0x0b8 > +#define QSERDES_V4_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V4_COM_DEC_START_MODE1 0x0c4 > #define QSERDES_V4_COM_DIV_FRAC_START1_MODE0 0x0cc > #define QSERDES_V4_COM_DIV_FRAC_START2_MODE0 0x0d0 > @@ -1106,8 +1106,8 @@ > #define QSERDES_V5_COM_LOCK_CMP1_MODE0 0x0ac > #define QSERDES_V5_COM_LOCK_CMP2_MODE0 0x0b0 > #define QSERDES_V5_COM_LOCK_CMP1_MODE1 0x0b4 > -#define QSERDES_V5_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V5_COM_LOCK_CMP2_MODE1 0x0b8 > +#define QSERDES_V5_COM_DEC_START_MODE0 0x0bc > #define QSERDES_V5_COM_DEC_START_MODE1 0x0c4 > #define QSERDES_V5_COM_DIV_FRAC_START1_MODE0 0x0cc > #define QSERDES_V5_COM_DIV_FRAC_START2_MODE0 0x0d0 > @@ -1134,8 +1134,8 @@ > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE1_MODE0 0x1ac > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE2_MODE0 0x1b0 > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE1_MODE1 0x1b4 > -#define QSERDES_V5_COM_BIN_VCOCAL_HSCLK_SEL 0x1bc > #define QSERDES_V5_COM_BIN_VCOCAL_CMP_CODE2_MODE1 0x1b8 > +#define QSERDES_V5_COM_BIN_VCOCAL_HSCLK_SEL 0x1bc > > /* Only for QMP V5 PHY - TX registers */ > #define QSERDES_V5_TX_RES_CODE_LANE_TX 0x34 -- With best wishes Dmitry -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-06-23 11:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 12:03 [PATCH 0/3] phy: qcom-qmp: clean up defines Johan Hovold 2022-06-09 12:03 ` Johan Hovold 2022-06-09 12:03 ` [PATCH 1/3] phy: qcom-qmp: clean up v4 and v5 define order Johan Hovold 2022-06-09 12:03 ` Johan Hovold 2022-06-23 11:49 ` Dmitry Baryshkov [this message] 2022-06-23 11:49 ` Dmitry Baryshkov 2022-06-09 12:03 ` [PATCH 2/3] phy: qcom-qmp: clean up define alignment Johan Hovold 2022-06-09 12:03 ` Johan Hovold 2022-06-09 12:03 ` [PATCH 3/3] phy: qcom-qmp: clean up hex defines Johan Hovold 2022-06-09 12:03 ` Johan Hovold 2022-06-23 11:50 ` Dmitry Baryshkov 2022-06-23 11:50 ` Dmitry Baryshkov 2022-06-23 11:45 ` [PATCH 0/3] phy: qcom-qmp: clean up defines Johan Hovold 2022-06-23 11:45 ` Johan Hovold 2022-07-05 7:12 ` Vinod Koul 2022-07-05 7:12 ` Vinod Koul
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=80da3045-5351-5d21-ffb2-e514e0b25961@linaro.org \ --to=dmitry.baryshkov@linaro.org \ --cc=agross@kernel.org \ --cc=bjorn.andersson@linaro.org \ --cc=johan+linaro@kernel.org \ --cc=kishon@ti.com \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-phy@lists.infradead.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.