From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Raag Jadav <raag.jadav@intel.com>
Subject: Re: [PATCH v1 1/2] pinctrl: cherryview: Avoid duplicated I/O
Date: Fri, 6 Oct 2023 13:26:45 +0300 [thread overview]
Message-ID: <ZR/g5SwjBOSN4agw@smile.fi.intel.com> (raw)
In-Reply-To: <20231006102412.GY3208943@black.fi.intel.com>
On Fri, Oct 06, 2023 at 01:24:12PM +0300, Mika Westerberg wrote:
> On Fri, Oct 06, 2023 at 12:40:32PM +0300, Andy Shevchenko wrote:
> > In some cases we already read the value from the register followed
> > by a reading of it again for other purposes, but the both reads
> > are under the lock and bits we are insterested in are not going
> > to change (they are not volatile from HW perspective). Hence, no
> > need to read the same registeer twice.
>
> Typo "registeer" -> "register"
Will fix when applying.
...
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Thank you!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-10-06 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 9:40 [PATCH v1 1/2] pinctrl: cherryview: Avoid duplicated I/O Andy Shevchenko
2023-10-06 9:40 ` [PATCH v1 2/2] pinctrl: cherryview: Simplify code with cleanup helpers Andy Shevchenko
2023-10-06 10:26 ` Mika Westerberg
2023-10-06 10:32 ` Andy Shevchenko
2023-10-06 10:37 ` Andy Shevchenko
2023-10-06 10:24 ` [PATCH v1 1/2] pinctrl: cherryview: Avoid duplicated I/O Mika Westerberg
2023-10-06 10:26 ` Andy Shevchenko [this message]
2023-10-06 10:38 ` Andy Shevchenko
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=ZR/g5SwjBOSN4agw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raag.jadav@intel.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.