diff options
| author | Jim Wylder <jwylder@google.com> | 2024-05-23 16:14:36 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-07-11 12:47:17 +0200 |
| commit | 85646d77962cad6c4fcdc24bdf11fe8982fcd28f (patch) | |
| tree | ceb26e71ae2cdb34f640e6063f49e78c4a5cfd91 /drivers/platform | |
| parent | 62fc41a69c998d1b7a9472f6dc1498bf41ef8c88 (diff) | |
| download | linux-85646d77962cad6c4fcdc24bdf11fe8982fcd28f.tar.gz linux-85646d77962cad6c4fcdc24bdf11fe8982fcd28f.tar.bz2 linux-85646d77962cad6c4fcdc24bdf11fe8982fcd28f.zip | |
regmap-i2c: Subtract reg size from max_write
[ Upstream commit 611b7eb19d0a305d4de00280e4a71a1b15c507fc ]
Currently, when an adapter defines a max_write_len quirk,
the data will be chunked into data sizes equal to the
max_write_len quirk value. But the payload will be increased by
the size of the register address before transmission. The
resulting value always ends up larger than the limit set
by the quirk.
Avoid this error by setting regmap's max_write to the quirk's
max_write_len minus the number of bytes for the register and
padding. This allows the chunking to work correctly for this
limited case without impacting other use-cases.
Signed-off-by: Jim Wylder <jwylder@google.com>
Link: https://msgid.link/r/20240523211437.2839942-1-jwylder@google.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/platform')
0 files changed, 0 insertions, 0 deletions