From: Heiko Schocher <hs@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Jim Liu <jim.t90615@gmail.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Philip Richard Oberfichtner <pro@denx.de>
Subject: Please pull u-boot-i2c
Date: Thu, 2 Nov 2023 15:10:44 +0100 [thread overview]
Message-ID: <6b4f373a-b81b-e937-cdfb-83d49e4e4e37@denx.de> (raw)
Hello Tom,
please pull from u-boot-i2c:
The following changes since commit d9650a48234058c645d1a07951c3d2cf129427e6:
Merge branch '2023-10-28-assorted-platform-updates' (2023-10-28 09:23:27 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-i2c.git tags/i2cfixes-for-v2024-01-rc2
for you to fetch changes up to 5b6ee512ceb8d990e010646c4fe7b8a3633fad68:
bootcount: Add driver model I2C driver (2023-10-31 09:09:04 +0100)
----------------------------------------------------------------
i2c updates for v2024.01-rc2
- nuvoton: support standard/fast/fast plus mode
- bootcount: remove legacy i2c driver and implement
DM based version
Bugfixes:
- designware_i2c: adjust timing calculation
SPL probing failed on the StarFive VisionFive 2 board
Heinrich fixed this, by syncing timing calculation with
linux implementation.
----------------------------------------------------------------
Heinrich Schuchardt (1):
i2c: designware_i2c: adjust timing calculation
Jim Liu (1):
i2c: nuvoton: remove standard mode only
Philip Richard Oberfichtner (3):
bootcount: Remove legacy I2C driver
i2c: Implement i2c_get_chip_by_phandle()
bootcount: Add driver model I2C driver
drivers/bootcount/Kconfig | 34 +++++++++++++---------------------
drivers/bootcount/Makefile | 2 +-
drivers/bootcount/bootcount_dm_i2c.c | 102
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/bootcount/bootcount_i2c.c | 43 -------------------------------------------
drivers/i2c/designware_i2c.c | 19 +++++++++++++++----
drivers/i2c/i2c-uclass.c | 75
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/npcm_i2c.c | 5 -----
include/i2c.h | 12 ++++++++++++
8 files changed, 218 insertions(+), 74 deletions(-)
create mode 100644 drivers/bootcount/bootcount_dm_i2c.c
delete mode 100644 drivers/bootcount/bootcount_i2c.c
azure build is fine:
https://dev.azure.com/hs0298/hs/_build/results?buildId=109&view=results
Thanks!
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: hs@denx.de
next reply other threads:[~2023-11-02 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 14:10 Heiko Schocher [this message]
2023-11-02 14:53 ` Please pull u-boot-i2c Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 13:36 Heiko Schocher
2026-05-14 17:55 ` Tom Rini
2026-01-07 7:15 Heiko Schocher
2026-01-07 21:07 ` Tom Rini
2024-10-21 8:27 Heiko Schocher
2024-10-21 16:39 ` Tom Rini
2024-08-08 8:42 Heiko Schocher
2024-08-08 13:58 ` Tom Rini
2024-08-08 14:06 ` Heiko Schocher
2024-08-08 14:52 ` Tom Rini
2023-08-15 7:53 Heiko Schocher
2023-08-15 16:59 ` Tom Rini
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=6b4f373a-b81b-e937-cdfb-83d49e4e4e37@denx.de \
--to=hs@denx.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=jim.t90615@gmail.com \
--cc=pro@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 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.