From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jim Wylder <jwylder@google.com>,
broonie@kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH AUTOSEL 4.19 1/8] regmap: Account for register length when chunking
Date: Fri, 16 Jun 2023 21:38:16 +0200 [thread overview]
Message-ID: <ZIy6KMbGTS9AU3JY@duo.ucw.cz> (raw)
In-Reply-To: <20230615113956.649736-1-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hi!
> Currently, when regmap_raw_write() splits the data, it uses the
> max_raw_write value defined for the bus. For any bus that includes
> the target register address in the max_raw_write value, the chunked
> transmission will always exceed the maximum transmission length.
> To avoid this problem, subtract the length of the register and the
> padding from the maximum transmission.
>
> Signed-off-by: Jim Wylder <jwylder@google.com
> Link: https://lore.kernel.org/r/20230517152444.3690870-2-jwylder@google.com
> Signed-off-by: Mark Brown <broonie@kernel.org
> Signed-off-by: Sasha Levin <sashal@kernel.org>
Some ">"s are missing in the email addresses.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2023-06-16 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:39 Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 2/8] scsi: target: iscsi: Prevent login threads from racing between each other Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 3/8] HID: google: add jewel USB id Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 4/8] HID: wacom: Add error check to wacom_parse_and_register() Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 5/8] arm64: Add missing Set/Way CMO encodings Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 6/8] media: cec: core: don't set last_initiator if tx in progress Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 7/8] nfcsim.c: Fix error checking for debugfs_create_dir Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 4.19 8/8] usb: gadget: udc: fix NULL dereference in remove() Sasha Levin
2023-06-16 19:38 ` Pavel Machek [this message]
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=ZIy6KMbGTS9AU3JY@duo.ucw.cz \
--to=pavel@denx.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwylder@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®