From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH 1/3] SCSI: Allow platform-specific code to be run against the SCSI tree Date: Mon, 10 Aug 2009 17:11:47 +0100 Message-ID: <20090810161147.GA27277@srcf.ucam.org> References: <1247518987-10818-1-git-send-email-mjg@redhat.com> <20090810133815.GB22763@srcf.ucam.org> <1249916125.4089.4.camel@mulgrave.site> <20090810145809.GD24956@srcf.ucam.org> <1249920187.4089.129.camel@mulgrave.site> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1249920187.4089.129.camel@mulgrave.site> Sender: linux-scsi-owner@vger.kernel.org To: James Bottomley 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 List-Id: linux-acpi@vger.kernel.org On Mon, Aug 10, 2009 at 11:03:07AM -0500, James Bottomley wrote: > On Mon, 2009-08-10 at 15:58 +0100, Matthew Garrett wrote: > > 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. > > It's hard for me to comment without seeing the scsi_platform_register > code, but it strikes me that the only SCSI piece it's using is the > scsi_bus ... what else is SCSI specific in there? http://lkml.org/lkml/2009/7/13/286 is the ACPI implementation. I guess that it could be done entirely in libata if the bus structure is exported, but that does then limit it to ata - the code would need to be duplicated if anyone wants to bind scsi devices. I've no real preference, but this was the implementation suggested when I last posted this stuff back in 2005 or so. -- Matthew Garrett | mjg59@srcf.ucam.org