From: Francesco Dolcini <francesco@dolcini.it>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org,
Stefan Eichenberger <stefan.eichenberger@toradex.com>,
Trent Piepho <tpiepho@impinj.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v1] rtc: snvs: Allow a time difference on clock register read
Date: Fri, 4 Nov 2022 09:45:01 +0100 [thread overview]
Message-ID: <Y2TRDdCc+kl/J3DO@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <Y2RAbLzvNJDRocgZ@mail.local>
On Thu, Nov 03, 2022 at 11:27:56PM +0100, Alexandre Belloni wrote:
> On 03/11/2022 12:13:09+0100, Francesco Dolcini wrote:
> > From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> >
> > On an iMX6ULL the following message appears when a wakealarm is set:
> >
> > echo 0 > /sys/class/rtc/rtc1/wakealarm
> > rtc rtc1: Timeout trying to get valid LPSRT Counter read
> >
> > This does not always happen but is reproducible quite often (7 out of 10
> > times). The problem appears because the iMX6ULL is not able to read the
> > registers within one 32kHz clock cycle which is the base clock of the
> > RTC. Therefore, this patch allows a difference of up to 320 cycles
> > (10ms). 10ms was chosen to be big enough even on systems with less cpu
> > power (e.g. iMX6ULL). According to the reference manual a difference is
> > fine:
> > - If the two consecutive reads are similar, the value is correct.
> > The values have to be similar, not equal.
> >
> > Fixes: cd7f3a249dbe ("rtc: snvs: Add timeouts to avoid kernel lockups")
> > Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> > Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> Also, your SoB needs to match the sender address.
I'll fix it.
However there is something that I do not fully understand and I thought
it was not strictly required when forwarding patches like I just did.
How do you handle the very common case in which the patch author is the
corporate email address, but the email sender is a private one?
Normally you have:
- sender me@personal.example.com
- first line of the email From: me@company.example.com
- SoB: me@company.example.com
with that the email sender does not match the last sob, but this is very
common, see for example https://lore.kernel.org/all/20220705085825.21255-1-max.oss.09@gmail.com/
Should we have an additional
- sob me@personal.example.com
Therefore having 2 sob by the same individual, but with 2 different email
addresses?
Francesco
next prev parent reply other threads:[~2022-11-04 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 11:13 [PATCH v1] rtc: snvs: Allow a time difference on clock register read Francesco Dolcini
2022-11-03 22:27 ` Alexandre Belloni
2022-11-04 8:36 ` Francesco Dolcini
2022-11-04 9:11 ` Alexandre Belloni
2022-11-03 22:27 ` Alexandre Belloni
2022-11-04 8:45 ` Francesco Dolcini [this message]
2022-11-04 9:09 ` Alexandre Belloni
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=Y2TRDdCc+kl/J3DO@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=francesco.dolcini@toradex.com \
--cc=linux-rtc@vger.kernel.org \
--cc=stefan.eichenberger@toradex.com \
--cc=tpiepho@impinj.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).