From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jan Dabros <jsd@semihalf.com>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, wsa@kernel.org,
rrangel@chromium.org, mw@semihalf.com, jaz@semihalf.com,
upstream@semihalf.com
Subject: Re: [RFC 1/2] i2c: designware: Add missing locks
Date: Thu, 23 Dec 2021 16:29:56 +0200 [thread overview]
Message-ID: <443785f5-323e-e36f-7a10-12d03140e6b0@linux.intel.com> (raw)
In-Reply-To: <20211222094558.2098791-2-jsd@semihalf.com>
On 12/22/21 11:45, Jan Dabros wrote:
> All accesses to controller's registers should be protected on
> probe, disable and xfer paths. This is needed for i2c bus controllers
> that are shared with but not controlled by kernel.
>
> Signed-off-by: Jan Dabros <jsd@semihalf.com>
> ---
> drivers/i2c/busses/i2c-designware-common.c | 12 ++++++++++++
> drivers/i2c/busses/i2c-designware-master.c | 6 ++++++
> 2 files changed, 18 insertions(+)
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2021-12-23 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 9:45 [RFC 0/2] i2c-designware: Add support for AMD PSP semaphore Jan Dabros
2021-12-22 9:45 ` [RFC 1/2] i2c: designware: Add missing locks Jan Dabros
2021-12-23 14:29 ` Jarkko Nikula [this message]
2021-12-23 15:50 ` Andy Shevchenko
2021-12-27 7:17 ` Jan Dąbroś
2021-12-22 9:45 ` [RFC 2/2] i2c: designware: Add AMD PSP I2C bus support Jan Dabros
2021-12-23 14:37 ` Jarkko Nikula
2021-12-27 11:34 ` Jan Dąbroś
2021-12-22 11:46 ` [RFC 0/2] i2c-designware: Add support for AMD PSP semaphore Andy Shevchenko
2021-12-22 17:56 ` Serge Semin
2021-12-22 18:21 ` Andy Shevchenko
2021-12-22 21:51 ` Jan Dąbroś
2021-12-25 15:58 ` Andy Shevchenko
2021-12-27 7:00 ` Jan Dąbroś
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=443785f5-323e-e36f-7a10-12d03140e6b0@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jaz@semihalf.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mw@semihalf.com \
--cc=rrangel@chromium.org \
--cc=upstream@semihalf.com \
--cc=wsa@kernel.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;
as well as URLs for NNTP newsgroup(s).