All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
	Huang Ying <ying.huang@intel.com>,
	Bob Moore <robert.moore@intel.com>,
	linux-acpi@vger.kernel.org, bondd@us.ibm.com,
	Myron Stowe <myron.stowe@redhat.com>
Subject: Re: [PATCH 2/2] ACPICA: support Generic Address Structure bit_offset in acpi_read/write
Date: Fri, 18 Nov 2011 00:10:10 +0100	[thread overview]
Message-ID: <201111180010.11173.rjw@sisk.pl> (raw)
In-Reply-To: <CAErSpo4TC-M31rp1fHw6ZsTHehAsXi-6eGmLEpNytiL-ez+iLQ@mail.gmail.com>

On Thursday, November 17, 2011, Bjorn Helgaas wrote:
> On Wed, Nov 16, 2011 at 4:27 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, November 16, 2011, Bjorn Helgaas wrote:
> 
> >> We should try very hard to treat APEI generic address structures the
> >> same way as all others.  If that means some machines need firmware
> >> upgrades or some sort of quirks to work around BIOS bugs, we might
> >> have to accept that.  I think a single set of GAS accessors plus a few
> >> quirks that fix the GAS structures is far better than having
> >> APEI-specific GAS accessors that are basically tailored to a few
> >> broken machines.
> >
> > We can use APEI-specific wrappers around generic GAS accessors, though.
> 
> Yes, but IMHO, we should only need wrappers to support APEI-specific
> functionality, e.g., the mask.
> 
> Here's an attempt to lay out how I think acpi_read() and acpi_write()
> *should* work:
> 
> https://docs.google.com/spreadsheet/ccc?key=0AjvKas55tQpqdElKVXM2TEFVcnI3SjVuZ1pqUENMN1E
> 
> I think the proposed behavior is compatible with the APEI assumptions
> in the current code.  Please comment :)

Well, I'd express access_width in multiples of 8.  Or perhaps use a mask?

I'm afraid it may be difficult to get right by the callers, however.

Thanks,
Rafael

  reply	other threads:[~2011-11-17 23:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 23:05 [PATCH 0/2] acpi_read() bit_offset support Bjorn Helgaas
2011-11-11 23:05 ` [PATCH 1/2] ACPICA: acpi_read: update return value atomically Bjorn Helgaas
2011-11-11 23:05 ` [PATCH 2/2] ACPICA: support Generic Address Structure bit_offset in acpi_read/write Bjorn Helgaas
2011-11-15 15:13   ` Bjorn Helgaas
2011-11-15 16:49     ` Thomas Renninger
2011-11-16 15:45       ` Bjorn Helgaas
2011-11-16 19:58         ` Thomas Renninger
2011-11-17  0:15           ` Bjorn Helgaas
2011-12-12 15:39             ` Thomas Renninger
2011-11-16 23:27         ` Rafael J. Wysocki
2011-11-16 23:59           ` Bjorn Helgaas
2011-11-17 23:10             ` Rafael J. Wysocki [this message]
2011-11-17  0:51           ` Huang Ying
2011-11-17 20:27             ` Rafael J. Wysocki
2011-11-17 23:38               ` Thomas Renninger
2011-11-18  9:27                 ` Rafael J. Wysocki
2011-11-18  1:04               ` Huang Ying
2011-11-18  9:25                 ` Rafael J. Wysocki
2011-11-21  7:51                   ` Huang Ying
2011-11-21 10:08                     ` Russell King - ARM Linux
2011-11-28 23:03                     ` Luck, Tony
2011-11-29  2:15                       ` Huang Ying
2011-11-30 21:54                         ` Luck, Tony
2011-12-01  0:49                           ` Huang Ying
2011-12-01  0:53                             ` Luck, Tony
2011-12-01  0:57                               ` Huang Ying
2011-12-01  1:03                                 ` Luck, Tony
2011-12-01  1:11                                   ` Huang Ying
2011-12-01 17:35                                     ` Luck, Tony
2011-12-02  1:48                                       ` Huang Ying

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=201111180010.11173.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=bhelgaas@google.com \
    --cc=bondd@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=myron.stowe@redhat.com \
    --cc=robert.moore@intel.com \
    --cc=trenn@suse.de \
    --cc=ying.huang@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.