From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: "Winiarska, Iwona" <iwona.winiarska@intel.com>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "billy_tsai@aspeedtech.com" <billy_tsai@aspeedtech.com>
Subject: Re: [PATCH] peci: aspeed: Clear clock_divider value before setting it
Date: Fri, 19 Apr 2024 08:55:51 +0930 [thread overview]
Message-ID: <1583360debaee14a988e4019cf30250f6eb4d8da.camel@codeconstruct.com.au> (raw)
In-Reply-To: <7520ac6ef7afae66f9b1636e5806ff2bfd93584d.camel@intel.com>
On Thu, 2024-04-18 at 13:41 +0000, Winiarska, Iwona wrote:
> On Thu, 2024-04-18 at 09:11 +0930, Andrew Jeffery wrote:
> > Hi Iwona,
> >
> > On Wed, 2024-04-17 at 15:48 +0200, Iwona Winiarska wrote:
> > > PECI clock divider is programmed on 10:8 bits of PECI Control register.
> > > Before setting a new value, clear bits read from hardware.
> > >
> > > Signed-off-by: Iwona Winiarska <iwona.winiarska@intel.com>
> >
> > I think it would be best to add a Fixes: tag and Cc: stable in
> > accordance with the stable tree rules. Are you happy to do so?
>
> Hi!
>
> Technically, the initial value of this register should be 0, but I've added the
> clear just to be on the safe side and to not have to rely on that.
Yeah, it could cause havoc with an unbind/bind sequence if people are
messing with the clocks in between.
> I don't think we're ever programming invalid values in the real-world scenarios,
> and because of that - I don't think this is stable material.
Right, I don't expect people are doing the above in environments where
stability is a concern.
Thanks for elaborating.
Andrew
next prev parent reply other threads:[~2024-04-18 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 13:48 Iwona Winiarska
2024-04-17 23:41 ` Andrew Jeffery
2024-04-18 13:41 ` Winiarska, Iwona
2024-04-18 23:25 ` Andrew Jeffery [this message]
2024-06-12 2:23 ` Billy Tsai
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=1583360debaee14a988e4019cf30250f6eb4d8da.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=iwona.winiarska@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
/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
all inboxes | Powered by JetHome®