[PATCH 0/3] libata: prevent writes to read-only registers

From	Doug Berger <opendmb@gmail.com>
Newsgroups	linux.kernel
Subject	[PATCH 0/3] libata: prevent writes to read-only registers
Date	2017-06-22 01:30 +0200
Message-ID	<tUXep-4FF-9@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View 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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[PATCH 0/3] libata: prevent writes to read-only registers Doug Berger <opendmb@gmail.com> - 2017-06-22 01:30 +0200
  [PATCH 1/3] libata: Add the AHCI_HFLAG_YES_ALPM flag Doug Berger <opendmb@gmail.com> - 2017-06-22 01:30 +0200
  [PATCH 2/3] libata: Add the AHCI_HFLAG_NO_WRITE_TO_RO flag Doug Berger <opendmb@gmail.com> - 2017-06-22 01:30 +0200
  Re: [PATCH 0/3] libata: prevent writes to read-only registers Tejun Heo <tj@kernel.org> - 2017-06-22 22:20 +0200

csiph-web