From: Doug Berger <opendmb@gmail.com>
To: tj@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Doug Berger <opendmb@gmail.com>
Subject: [PATCH 0/3] libata: prevent writes to read-only registers
Date: Wed, 21 Jun 2017 16:20:11 -0700 [thread overview]
Message-ID: <20170621232014.27790-1-opendmb@gmail.com> (raw)
Recent Broadcom SoCs allow for the trapping of write accesses to
read-only registers. This is only useful if such accesses are
exceptional, so it is desirable to prevent such accesses in normal
operation. To that end, this set of commits proposes adding two
flags to the libata core.
The first allows for a quirk that exists in some Broadcom devices
that are capable of supporting Aggresive Link Power Management even
though it is not reported by their read-only capability register.
This removes a need for the Broadcom driver to write to it's
read-only capability register.
The second is a notification to the libata-core that it should not
write to any standard registers that are defined to be read-only.
The Broadcom driver is then modified to use these two general
purpose flags.
Doug Berger (3):
libata: Add the AHCI_HFLAG_YES_ALPM flag
libata: Add the AHCI_HFLAG_NO_WRITE_TO_RO flag
ata: ahci_brcm: Avoid writing to read-only registers
drivers/ata/ahci.h | 3 +++
drivers/ata/ahci_brcm.c | 12 ++++--------
drivers/ata/libahci.c | 8 +++++++-
3 files changed, 14 insertions(+), 9 deletions(-)
--
2.13.0
next reply other threads:[~2017-06-21 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 23:20 Doug Berger [this message]
2017-06-21 23:20 ` [PATCH 1/3] libata: Add the AHCI_HFLAG_YES_ALPM flag Doug Berger
2017-06-21 23:20 ` [PATCH 2/3] libata: Add the AHCI_HFLAG_NO_WRITE_TO_RO flag Doug Berger
2017-06-21 23:20 ` [PATCH 3/3] ata: ahci_brcm: Avoid writing to read-only registers Doug Berger
2017-06-22 20:13 ` [PATCH 0/3] libata: prevent writes " Tejun Heo
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=20170621232014.27790-1-opendmb@gmail.com \
--to=opendmb@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).