From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Adrian Huang <adrianhuang0701@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, Adrian Huang <ahuang12@lenovo.com>,
Dong Wang <wangdong28@lenovo.com>
Subject: Re: [PATCH v2 1/1] i2c: designware: Fix wrong setting for {ss,fs,hs}_{h,l}cnt registers
Date: Mon, 5 Aug 2024 17:27:30 +0300 [thread overview]
Message-ID: <59353915-2360-42e7-b38d-ca64d59f5b45@linux.intel.com> (raw)
In-Reply-To: <20240802130143.26908-1-ahuang12@lenovo.com>
On 8/2/24 4:01 PM, Adrian Huang wrote:
> From: Adrian Huang <ahuang12@lenovo.com>
>
> When disabling CONFIG_X86_AMD_PLATFORM_DEVICE option, the driver
> 'drivers/acpi/acpi_apd.c' won't be compiled. This leads to a situation
> where BMC (Baseboard Management Controller) cannot retrieve the memory
> temperature via the i2c interface after i2c DW driver is loaded. Note
> that BMC can retrieve the memory temperature before booting into OS.
>
> [Debugging Detail]
> 1. dev->pclk and dev->clk are NULL when calling devm_clk_get_optional()
> in dw_i2c_plat_probe().
>
> 2. The callings of i2c_dw_scl_hcnt() in i2c_dw_set_timings_master()
> return 65528 (-8 in integer format) or 65533 (-3 in integer format).
> The following log shows SS's HCNT/LCNT:
>
> i2c_designware AMDI0010:01: Standard Mode HCNT:LCNT = 65533:65535
>
> 3. The callings of i2c_dw_scl_lcnt() in i2c_dw_set_timings_master()
> return 65535 (-1 in integer format). The following log shows SS's
> HCNT/LCNT:
>
> i2c_designware AMDI0010:01: Fast Mode HCNT:LCNT = 65533:65535
>
> 4. i2c_dw_init_master() configures the register IC_SS_SCL_HCNT with
> the value 65533. However, the DW i2c databook mentioned the value
> cannot be higher than 65525. Quote from the DW i2c databook:
>
> NOTE: This register must not be programmed to a value higher than
> 65525, because DW_apb_i2c uses a 16-bit counter to flag an
> I2C bus idle condition when this counter reaches a value of
> IC_SS_SCL_HCNT + 10.
>
> 5. Since ss_hcnt, ss_lcnt, fs_hcnt, and fs_lcnt are the invalid
> values, we should not write the corresponding registers.
>
> Fix the issue by reading dev->{ss,fs,hs}_hcnt and dev->{ss,fs,hs}_lcnt
> from HW registers if ic_clk is not set.
>
> Link: https://lore.kernel.org/linux-i2c/8295cbe1-a7c5-4a35-a189-5d0bff51ede6@linux.intel.com/
> Suggested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> Reported-by: Dong Wang <wangdong28@lenovo.com>
> Tested-by: Dong Wang <wangdong28@lenovo.com>
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2024-08-05 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 13:01 [PATCH v2 1/1] i2c: designware: Fix wrong setting for {ss,fs,hs}_{h,l}cnt registers Adrian Huang
2024-08-05 14:27 ` Jarkko Nikula [this message]
2024-08-05 17:26 ` Andi Shyti
2024-08-06 12:10 ` Huang Adrian
2024-08-12 17:13 ` Andy Shevchenko
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=59353915-2360-42e7-b38d-ca64d59f5b45@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wangdong28@lenovo.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