[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090810145809.GD24956@srcf.ucam.org>
Date: Mon, 10 Aug 2009 15:58:09 +0100
From: Matthew Garrett <mjg@...hat.com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: linux-acpi@...r.kernel.org, linux-scsi@...r.kernel.org,
shaohua.li@...el.com, linux-ide@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] SCSI: Allow platform-specific code to be run
against the SCSI tree
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@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists