mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	jgarzik@pobox.com, rdunlap@xenotime.net
Subject: Re: [patch 1/2] libata: _GTF support
Date: Fri, 29 Sep 2006 10:03:00 -0700	[thread overview]
Message-ID: <20060929100300.ff76a22d.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <20060929020707.GA22082@srcf.ucam.org>

On Fri, 29 Sep 2006 03:07:07 +0100
Matthew Garrett <mjg59@srcf.ucam.org> wrote:

> On Thu, Sep 28, 2006 at 11:29:01AM -0700, Kristen Carlson Accardi wrote:
> 
> I mentioned this to Randy a while back, but I can't remember what sort 
> of resolution we came to. In any case:
> 
> > + * sata_get_dev_handle - finds acpi_handle and PCI device.function
> 
> I'm a bit uncomfortable that we seem to have two quite different ways of 
> accomplishing much the same thing. On the PCI bus, we have a callback 
> that gets triggered whenever a new PCI device is attached. At that 
> point, we look for the associated ACPI object and put a pointer to that 
> in the device structure. Then, whenever we want to make an ACPI call, we 
> can simply refer to that.
> 
> This implementation seems to reimplement much of the same lookup code, 
> but makes it libata specific. Wouldn't it be cleaner to implement it in 
> a similar way to PCI? The only real downside is that you need to add a 
> callback in the ata bus code. drivers/pci/pci-acpi.c/pci_acpi_init is 
> the sort of thing required.
> 
> (Thinking ahead, would that make it easier to maintain links in sysfs 
> between devices and acpi objects?)
> 
> -- 
> Matthew Garrett | mjg59@srcf.ucam.org

This makes sense to me.  I'm happy to put together some patches for 
commenting on if people think this is a good way to go.  It would be
much cleaner in my opinion and we could get rid of a good chunk of code.

Kristen

  parent reply	other threads:[~2006-09-29 17:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060928182211.076258000@localhost.localdomain>
2006-09-28 18:29 ` Kristen Carlson Accardi
2006-09-28 18:51   ` Diego Calleja
2006-09-28 20:32     ` Jeff Garzik
2006-09-28 20:39   ` Jeff Garzik
2006-09-29  2:07   ` Matthew Garrett
2006-09-29 16:54     ` Kristen Carlson Accardi
2006-09-29 17:04       ` Randy Dunlap
2006-09-29 17:03     ` Kristen Carlson Accardi [this message]
2006-10-01 17:02   ` Andrey Borzenkov
2006-10-02 16:45     ` Kristen Carlson Accardi
2006-10-02 13:06   ` Pavel Machek
2006-09-28 18:29 ` [patch 2/2] libata: _SDD support Kristen Carlson Accardi
2006-09-29  2:13   ` Matthew Garrett
2006-09-30  0:33     ` Kristen Carlson Accardi
2006-11-11  0:14     ` [patch] libata: change order of _SDD/_GTF execution (resend #3) Kristen Carlson Accardi
2006-11-14 19:19       ` Jeff Garzik
2006-10-02 13:08   ` [patch 2/2] libata: _SDD support Pavel Machek
2006-09-28 18:29 ` [patch 1/2] libata: _GTF support Kristen Carlson Accardi
2006-09-28 18:30 ` Kristen Carlson Accardi
2006-09-28 18:30 ` [patch 2/2] libata: _SDD support Kristen Carlson Accardi
2006-09-29 17:56   ` Valdis.Kletnieks
     [not found] <20060927223441.205181000@localhost.localdomain>
2006-09-27 22:36 ` [patch 1/2] libata: _GTF support Kristen Carlson Accardi
2006-09-27 22:49   ` Jeff Garzik
2006-10-09 11:41   ` Stefan Seyfried
2006-10-09 15:10     ` Randy Dunlap

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=20060929100300.ff76a22d.kristen.c.accardi@intel.com \
    --to=kristen.c.accardi@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rdunlap@xenotime.net \
    /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

all inboxes | Powered by JetHome®