From: Colin Foster <colin.foster@in-advantage.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
alexis.lothore@bootlin.com
Subject: Re: [PATCH] regmap: don't check for alignment when using reg_shift
Date: Fri, 5 May 2023 10:19:29 -0700 [thread overview]
Message-ID: <ZFU6oepWPoYDJczo@euler> (raw)
In-Reply-To: <20230428094745.63677228@pc-7.home>
Hi Maxime,
On Fri, Apr 28, 2023 at 09:47:45AM +0200, Maxime Chevallier wrote:
> On Fri, 28 Apr 2023 09:30:10 +0200
> Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
>
> > Hello Mark, Colin,
> >
> > On Tue, 25 Apr 2023 13:56:23 +0100
> > Mark Brown <broonie@kernel.org> wrote:
> >
> > > On Fri, Apr 21, 2023 at 08:50:30AM -0700, Colin Foster wrote:
> > > > On Thu, Apr 20, 2023 at 05:06:17PM +0200, Maxime Chevallier
> > > > wrote:
> > >
> > > > > On regmap consumers that require address translation through
> > > > > up/downshifting, the alignment check in the regmap core doesn't
> > > > > take the translation into account. This doesn't matter when
> > > > > downshifting the register address, as any address that fits a
> > > > > given alignment requirement will still meet it when downshifted
> > > > > (a 4-byte aligned address will always also be 2-bytes aligned
> > > > > for example).
> > >
> > > > > However, when upshifting, this check causes spurious errors, as
> > > > > it occurs before the upshifting.
> > >
Sorry for a really delayed response, but I just got back around to
thinking about this. Crazy busy times for me.
What about an explicit parameter in regmap_config that will disable
alignment checks? That seems like it might be a welcome feature
addition.
Colin Foster
next prev parent reply other threads:[~2023-05-05 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:06 [PATCH] regmap: don't check for alignment when using reg_shift Maxime Chevallier
2023-04-21 15:50 ` Colin Foster
2023-04-25 12:56 ` Mark Brown
2023-04-28 7:30 ` Maxime Chevallier
2023-04-28 7:47 ` Maxime Chevallier
2023-05-05 17:19 ` Colin Foster [this message]
2023-05-06 0:18 ` Mark Brown
2023-05-11 6:52 ` Maxime Chevallier
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=ZFU6oepWPoYDJczo@euler \
--to=colin.foster@in-advantage.com \
--cc=alexis.lothore@bootlin.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=rafael@kernel.org \
--cc=thomas.petazzoni@bootlin.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 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.