From: Matthew Garrett <mjg@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-acpi@vger.kernel.org, linux-scsi@vger.kernel.org,
shaohua.li@intel.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree
Date: Mon, 10 Aug 2009 15:58:09 +0100 [thread overview]
Message-ID: <20090810145809.GD24956@srcf.ucam.org> (raw)
In-Reply-To: <1249916125.4089.4.camel@mulgrave.site>
On Mon, Aug 10, 2009 at 02:55:25PM +0000, James Bottomley wrote:
> On Mon, 2009-08-10 at 14:38 +0100, Matthew Garrett wrote:
> > On Mon, Jul 13, 2009 at 10:03:05PM +0100, Matthew Garrett wrote:
> > > In certain cases (such as ACPI) we want to be able to associate
> > > platform-specific data against the SCSI device tree. Handling this
> > > properly requires the ability to run platform code at SCSI init time.
> > > This patch adds stub functions that can be overridden if the platform
> > > defines CONFIG_SCSI_PLATFORM.
> >
> > James, any thoughts on this?
>
> Sorry, I'd thought this had all moved to libata so I'd stopped paying
> attention ... why are extra bits in SCSI necessary?
They're SCSI as far as the device tree is concerned, so the glue
callbacks have to be registered from the SCSI layer. The only
implementation so far is for ACPI and only covers libata, but it could
potentially also be used to tie bay devices to the ofw tree on
openfirmware systems.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-08-10 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:03 [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree Matthew Garrett
2009-07-13 21:03 ` [PATCH 2/3] libata: Bind the Linux device tree to the ACPI device tree Matthew Garrett
2009-07-13 21:03 ` [PATCH 3/3] libata: Migrate ACPI code over to new bindings Matthew Garrett
2009-08-06 6:54 ` [PATCH 2/3] libata: Bind the Linux device tree to the ACPI device tree Håkon Løvdal
2009-08-06 14:51 ` Matthew Garrett
2009-08-10 13:38 ` [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree Matthew Garrett
2009-08-10 14:55 ` James Bottomley
2009-08-10 14:58 ` Matthew Garrett [this message]
2009-08-10 16:03 ` James Bottomley
2009-08-10 16:11 ` Matthew Garrett
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=20090810145809.GD24956@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shaohua.li@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 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).