From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Li Yang <leoyang.li@nxp.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: Wed, 21 Aug 2019 13:24:13 +0200 [thread overview]
Message-ID: <20190821112413.GA27031@piout.net> (raw)
In-Reply-To: <20190821112142.GD5128@sirena.co.uk>
On 21/08/2019 12:21:42+0100, Mark Brown wrote:
> On Tue, Aug 20, 2019 at 01:33:14PM -0500, Li Yang wrote:
>
> > 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
>
> It's *essential*? Will innovation never cease?
>
To be clear, for some RTCs, its is the only way to accurately set the
time.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-21 11:24 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
2019-08-21 11:21 ` Mark Brown
2019-08-21 11:24 ` Alexandre Belloni [this message]
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=20190821112413.GA27031@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=biwen.li@nxp.com \
--cc=broonie@kernel.org \
--cc=leoyang.li@nxp.com \
--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 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.