mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pei Xiao <xiaopei01@kylinos.cn>
To: xiaopeitux@foxmail.com
Cc: vkoul@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5] phy: freescale: fsl-samsung-hdmi: fix build error in fsl_samsung_hdmi_phy_configure_pll_lock_det
Date: Fri, 17 Jan 2025 10:15:31 +0800	[thread overview]
Message-ID: <476dace4-92fb-4d92-a342-cffd6f77b8f1@kylinos.cn> (raw)
In-Reply-To: <CAHCN7xL7eMV2f04nURp3jCCmNZ0GSTY=uaOwoiht38AC4Oz0EQ@mail.gmail.com>


在 2025/1/17 09:59, Adam Ford 写道:
> On Mon, Jan 13, 2025 at 2:41 AM <xiaopeitux@foxmail.com> wrote:
>> From: Pei Xiao <xiaopei01@kylinos.cn>
>>
>> FIELD_PREP() checks that a value fits into the available bitfield,
>> but the index div equals to 4,is out of range.
>>
>> which gcc complains about:
>> In function ‘fsl_samsung_hdmi_phy_configure_pll_lock_det’,
>> inlined from ‘fsl_samsung_hdmi_phy_configure’ at
>> drivers/phy/freescale/phy-fsl-samsung-hdmi.c :470:2:
>> ././include/linux/compiler_types.h:542:38: error: call to ‘__compiletime_assert_538’
>> declared with attribute error: FIELD_PREP: value too large for the field
>>   542 |  _compiletime_assert(condition, msg, __compiletime_assert_,
>> __COUNTER__)
>>       |                                      ^
>> ././include/linux/compiler_types.h:523:4: note: in definition of
>> macro ‘__compiletime_assert’ 523 |    prefix ## suffix();
>>       |    ^~~~~~
>> ././include/linux/compiler_types.h:542:2: note: in expansion of macro
>> ‘_compiletime_assert’
>>   542 |  _compiletime_assert(condition, msg, __compiletime_assert_,
>>  __COUNTER__)
>>
>> REG12_CK_DIV_MASK only two bit, limit div to range 0~3,
>> so build error will fix.
>>
> LGTM.
>
> Reviewed-by:  Adam Ford <aford173@gmail.com>
loop Vkoul for email address was written incorrectly.
>> Fixes: d567679f2b6a ("phy: freescale: fsl-samsung-hdmi: Clean up fld_tg_code calculation")
>> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
>>
>> Changlog:
>> ---
>> V5: add return ret from Geert suggestion
>> V4: change to use if statement
>> V3: change to use do-while
>> V2: change to use logical AND
>> ---
>>  drivers/phy/freescale/phy-fsl-samsung-hdmi.c | 13 +++++++++++--
>>  1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
>> index 5eac70a1e858..6817ceabaab4 100644
>> --- a/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
>> +++ b/drivers/phy/freescale/phy-fsl-samsung-hdmi.c
>> @@ -325,7 +325,7 @@ to_fsl_samsung_hdmi_phy(struct clk_hw *hw)
>>         return container_of(hw, struct fsl_samsung_hdmi_phy, hw);
>>  }
>>
>> -static void
>> +static int
>>  fsl_samsung_hdmi_phy_configure_pll_lock_det(struct fsl_samsung_hdmi_phy *phy,
>>                                             const struct phy_config *cfg)
>>  {
>> @@ -341,6 +341,9 @@ fsl_samsung_hdmi_phy_configure_pll_lock_det(struct fsl_samsung_hdmi_phy *phy,
>>                         break;
>>         }
>>
>> +       if (unlikely(div == 4))
>> +               return -EINVAL;
>> +
>>         writeb(FIELD_PREP(REG12_CK_DIV_MASK, div), phy->regs + PHY_REG(12));
>>
>>         /*
>> @@ -364,6 +367,8 @@ fsl_samsung_hdmi_phy_configure_pll_lock_det(struct fsl_samsung_hdmi_phy *phy,
>>                FIELD_PREP(REG14_RP_CODE_MASK, 2) |
>>                FIELD_PREP(REG14_TG_CODE_HIGH_MASK, fld_tg_code >> 8),
>>                phy->regs + PHY_REG(14));
>> +
>> +       return 0;
>>  }
>>
>>  static unsigned long fsl_samsung_hdmi_phy_find_pms(unsigned long fout, u8 *p, u16 *m, u8 *s)
>> @@ -467,7 +472,11 @@ static int fsl_samsung_hdmi_phy_configure(struct fsl_samsung_hdmi_phy *phy,
>>         writeb(REG21_SEL_TX_CK_INV | FIELD_PREP(REG21_PMS_S_MASK,
>>                cfg->pll_div_regs[2] >> 4), phy->regs + PHY_REG(21));
>>
>> -       fsl_samsung_hdmi_phy_configure_pll_lock_det(phy, cfg);
>> +       ret = fsl_samsung_hdmi_phy_configure_pll_lock_det(phy, cfg);
>> +       if (ret) {
>> +               dev_err(phy->dev, "pixclock too large\n");
>> +               return ret;
>> +       }
>>
>>         writeb(REG33_FIX_DA | REG33_MODE_SET_DONE, phy->regs + PHY_REG(33));
>>
>> --
>> 2.25.1
>>

  reply	other threads:[~2025-01-17  2:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13  8:34 xiaopeitux
2025-01-17  1:59 ` Adam Ford
2025-01-17  2:15   ` Pei Xiao [this message]
2025-02-10 17:02     ` Vinod Koul
2025-02-11  2:10       ` Pei Xiao
2025-02-11 10:47         ` Vinod Koul
2025-02-07 15:40   ` Adam Ford

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=476dace4-92fb-4d92-a342-cffd6f77b8f1@kylinos.cn \
    --to=xiaopei01@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@kernel.org \
    --cc=xiaopeitux@foxmail.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

all inboxes | Powered by JetHome®