From: Ronan Dalton <Ronan.Dalton@alliedtelesis.co.nz>
To: "meaganlloyd@linux.microsoft.com" <meaganlloyd@linux.microsoft.com>
Cc: "tgopinath@linux.microsoft.com" <tgopinath@linux.microsoft.com>,
"code@tyhicks.com" <code@tyhicks.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"giometti@enneenne.com" <giometti@enneenne.com>,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"sashal@kernel.org" <sashal@kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231
Date: Mon, 4 May 2026 23:54:32 +0000 [thread overview]
Message-ID: <4c097ca4fffed215395ec5979f0f0f43ed85cb97.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <20260504-fd90667b1274c4e3a38a0604@linux.microsoft.com>
Hi Meagan,
On Mon, 2026-05-04 at 15:08 -0700, Meagan Lloyd wrote:
> > + case ds_1337:
> > + case ds_1339:
> > + case ds_1341:
> > + case ds_3231:
> > + ret = regmap_read(ds1307->regmap,
> > DS1337_REG_STATUS, &tmp);
> > + if (ret)
> > + return ret;
> > + if (tmp & DS1337_BIT_OSF)
> > + return -EINVAL;
> > + break;
>
> If you're going to re-arrange the block to be in somewhat of an
> order,
> perhaps put it above 1338 since 1337 < 1338.
I've ordered it this way based on the first case statement in each
block. Since ds_1337 > ds_1308, I've put the block below the block
starting with ds_1308. I could instead order it based on the last case
statement in each block, if you think that's better.
next prev parent reply other threads:[~2026-05-04 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 4:46 [PATCH] rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 Ronan Dalton
2026-05-01 5:14 ` Chris Packham
2026-05-04 22:08 ` Meagan Lloyd
2026-05-04 23:54 ` Ronan Dalton [this message]
2026-05-05 19:20 ` Meagan Lloyd
2026-05-05 22:24 ` Ronan Dalton
2026-05-06 1:41 ` Meagan Lloyd
2026-05-06 1:57 ` Ronan Dalton
2026-05-07 15:19 ` Tyler Hicks
2026-05-07 23:44 ` Ronan Dalton
2026-05-08 2:09 ` Meagan Lloyd
2026-05-08 3:27 ` Ronan Dalton
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=4c097ca4fffed215395ec5979f0f0f43ed85cb97.camel@alliedtelesis.co.nz \
--to=ronan.dalton@alliedtelesis.co.nz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=alexandre.belloni@bootlin.com \
--cc=code@tyhicks.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=meaganlloyd@linux.microsoft.com \
--cc=sashal@kernel.org \
--cc=tgopinath@linux.microsoft.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