From: Mark Brown <broonie@kernel.org>
To: Ansuel Smith <ansuelsmth@gmail.com>,
Jim Wylder <jwylder@google.com>, Xu Yilun <yilun.xu@intel.com>,
matthew.gerlach@linux.intel.com, Mark Brown <broonie@kernel.org>
Cc: stable@kernel.org
Subject: [PATCH 0/2] regmap: Redo fixes for raw I/O length restrictions
Date: Wed, 12 Jul 2023 12:16:38 +0100 [thread overview]
Message-ID: <20230712-regmap-max-transfer-v1-0-80e2aed22e83@kernel.org> (raw)
During the v6.4 release there was an attempt to address the fact that
the specification of maximum I/O sizes for raw buses in the core does
not take account of the register or pad bits in the maxium length.
After this was merged it was realised that there are number of custom
bus implementations in drivers which were relying on the prior behavior
in various ways.
This should be factored out into the core but that will require
coordination with all the buses involved so let's fall back to the
original interface and add the accounting to the I2C bus where the
omission was originally observed.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
regmap: Drop initial version of maximum transfer length fixes
regmap: Account for register length in SMBus I/O limits
drivers/base/regmap/regmap-i2c.c | 8 ++++----
drivers/base/regmap/regmap-spi-avmm.c | 2 +-
drivers/base/regmap/regmap.c | 6 ++----
3 files changed, 7 insertions(+), 9 deletions(-)
---
base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
change-id: 20230708-regmap-max-transfer-dadeb827143f
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-07-15 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 11:16 Mark Brown [this message]
2023-07-12 11:16 ` [PATCH 1/2] regmap: Drop initial version of maximum transfer length fixes Mark Brown
2023-07-12 11:16 ` [PATCH 2/2] regmap: Account for register length in SMBus I/O limits Mark Brown
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=20230712-regmap-max-transfer-v1-0-80e2aed22e83@kernel.org \
--to=broonie@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=jwylder@google.com \
--cc=matthew.gerlach@linux.intel.com \
--cc=stable@kernel.org \
--cc=yilun.xu@intel.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