From: Michael Wu <michael.wu@kneron.us>
To: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Morgan Chang <morgan.chang@kneron.us>,
mvp.kutali@gmail.com, Michael Wu <michael.wu@kneron.us>
Subject: [PATCH v3 0/2] Compute HS HCNT and LCNT based on HW parameters
Date: Tue, 1 Oct 2024 16:29:32 +0800 [thread overview]
Message-ID: <20241001082937.680372-1-michael.wu@kneron.us> (raw)
In commit 35eba185fd1a ("i2c: designware: Calculate SCL timing parameters for
High Speed Mode") hs_hcnt and hs_lcnt are computed based on fixed tHIGH = 160
and tLOW = 320. However, the set of these fixed values only applies to the
combination of hardware parameters "IC_CAP_LOADING = 400pF" and
"IC_FREQ_OPTIMIZATION = 1". Outside of this combination, SCL frequency may not
reach 3.4 MHz if hs_hcnt and hs_lcnt are both computed using these two fixed
values.
Since there are no any registers controlling these two hardware parameters,
their values can only be declared through the device tree.
v3:
- add vendor prefix on new property name
- read new properties in i2c_dw_fw_parse_and_configure() directly
- in i2c_dw_set_timings_master() check dev->bus_capacitance_pf and then decide
t_high and t_low
v2:
- provide more hardware information in dt-bindings
- rename "bus-loading" to "bus-capacitance-pf"
- call new i2c_dw_fw_parse_hw_params() in i2c_dw_fw_parse_and_configure() to
parse hardware parameters from the device tree.
Michael Wu (2):
dt-bindings: i2c: snps,designware-i2c: declare bus capacitance and clk
freq optimized
i2c: dwsignware: determine HS tHIGH and tLOW based on HW parameters
.../bindings/i2c/snps,designware-i2c.yaml | 24 +++++++++++++++++++
drivers/i2c/busses/i2c-designware-common.c | 5 ++++
drivers/i2c/busses/i2c-designware-core.h | 5 ++++
drivers/i2c/busses/i2c-designware-master.c | 23 ++++++++++++++++--
4 files changed, 55 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-01 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 8:29 Michael Wu [this message]
2024-10-01 8:29 ` [PATCH v3 1/2] dt-bindings: i2c: snps,designware-i2c: declare bus capacitance and clk freq optimized Michael Wu
2024-10-02 6:08 ` Krzysztof Kozlowski
2024-10-02 9:20 ` Michael Wu
2024-10-02 9:50 ` Krzysztof Kozlowski
2024-10-02 9:36 ` Michael Wu
2024-10-01 8:29 ` [PATCH v3 2/2] i2c: dwsignware: determine HS tHIGH and tLOW based on HW parameters Michael Wu
2024-10-01 11:14 ` Andi Shyti
2024-10-01 13:00 ` Andy Shevchenko
2024-10-02 9:31 ` Michael Wu
2024-10-02 14:17 ` 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=20241001082937.680372-1-michael.wu@kneron.us \
--to=michael.wu@kneron.us \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=morgan.chang@kneron.us \
--cc=mvp.kutali@gmail.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;
as well as URLs for NNTP newsgroup(s).