From: Li Yang <leoyang.li@nxp.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
nandor.han@vaisala.com, Biwen Li <biwen.li@nxp.com>,
a.zummo@towertech.it, linux-rtc@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [v2] rtc: pcf85363/pcf85263: fix error that failed to run hwclock -w
Date: Tue, 20 Aug 2019 13:33:14 -0500 [thread overview]
Message-ID: <CADRPPNQ__XRW74e+Dq0BEjJq-onVi2dmb7qKrn2Lt_xr50VCCw@mail.gmail.com> (raw)
In-Reply-To: <20190820182224.GI4738@sirena.co.uk>
On Tue, Aug 20, 2019 at 1:24 PM Mark Brown <broonie@kernel.org> wrote:
>
> On Fri, Aug 16, 2019 at 02:40:47PM -0500, Li Yang wrote:
> > On Fri, Aug 16, 2019 at 11:30 AM Alexandre Belloni
>
> > > Most of the i2c RTCs do address wrapping which is sometimes the only way
> > > to properly set the time.
>
> > Adding Mark and Nandor to the loop.
>
> Is there a specific question or something here?
Some of the RTC hardware has the capability of address wrapping which
means if you access a continuous address range across a certain
boundary(could be the boundary of a regmap region) the hardware
actually wrap the access to a lower address. But the address
violation check of regmap rejects such access. According to
Alexcandre, the address wrapping is essential to the functionality of
some RTC devices and can improve performance for some others. We are
wondering if it is reasonable to have regmap support this address
wrapping.
Regards,
Leo
next prev parent reply other threads:[~2019-08-20 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 2:46 [v2] rtc: pcf85363/pcf85263: fix error that failed to run hwclock -w Biwen Li
2019-08-16 8:04 ` Alexandre Belloni
2019-08-16 15:50 ` Li Yang
2019-08-16 16:28 ` Alexandre Belloni
2019-08-16 19:40 ` Li Yang
2019-08-20 18:22 ` Mark Brown
2019-08-20 18:33 ` Li Yang [this message]
2019-08-21 11:21 ` Mark Brown
2019-08-21 11:24 ` Alexandre Belloni
2019-08-21 11:30 ` Mark Brown
2019-08-21 11:38 ` Alexandre Belloni
2019-08-21 11:47 ` Mark Brown
2019-08-21 6:20 ` Nandor Han
2019-08-26 4:29 ` [EXT] " Biwen Li
2019-08-26 9:17 ` Nandor Han
2019-08-26 9:49 ` Biwen Li
2019-08-26 10:06 ` Alexandre Belloni
2019-08-26 10:40 ` Biwen Li
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=CADRPPNQ__XRW74e+Dq0BEjJq-onVi2dmb7qKrn2Lt_xr50VCCw@mail.gmail.com \
--to=leoyang.li@nxp.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=biwen.li@nxp.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=nandor.han@vaisala.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;
as well as URLs for NNTP newsgroup(s).