Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933844AbZJGQTm (ORCPT ); Wed, 7 Oct 2009 12:19:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759485AbZJGQTl (ORCPT ); Wed, 7 Oct 2009 12:19:41 -0400 Received: from va3ehsobe005.messaging.microsoft.com ([216.32.180.15]:4612 "EHLO VA3EHSOBE005.bigfish.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759461AbZJGQTk convert rfc822-to-8bit (ORCPT ); Wed, 7 Oct 2009 12:19:40 -0400 X-SpamScore: -34 X-BigFish: VPS-34(zz542N1432R98dN4015L9371Pzz1202hzzz2dh6bh61h) X-Spam-TCS-SCL: 0:0 X-FB-SS: 5, X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Subject: RE: Xilinx SYSACE driver and 8-bit attachment Date: Wed, 7 Oct 2009 09:18:40 -0700 In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Xilinx SYSACE driver and 8-bit attachment Thread-Index: AcpHXeJC9zSr90w5QgK5RFl0wxcnUgACw3kg References: <1d3f23370910070013u6307bc42hf7ab243b52d007df@mail.gmail.com> <192797ad-5dd4-4ebe-8db3-d381bb949e1e@VA3EHSMHS029.ehs.local> From: Stephen Neuendorffer To: "Grant Likely" , "John Linn" CC: "David DeBonis" , "devicetree-discuss" , "Linux Kernel list" , "Michal Simek" , "John Linn" , "John Williams" X-OriginalArrivalTime: 07 Oct 2009 16:18:49.0076 (UTC) FILETIME=[DA295340:01CA4769] Message-ID: <51ada07b-493e-4552-b79b-7a4044ae1b4c@VA3EHSMHS028.ehs.local> X-Reverse-DNS: unknown-60-83.xilinx.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3530 Lines: 73 > -----Original Message----- > From: devicetree-discuss-bounces+stephen.neuendorffer=xilinx.com@lists.ozlabs.org [mailto:devicetree- > discuss-bounces+stephen.neuendorffer=xilinx.com@lists.ozlabs.org] On Behalf Of Grant Likely > Sent: Wednesday, October 07, 2009 7:53 AM > To: John Linn > Cc: David DeBonis; Stephen Neuendorffer; devicetree-discuss; Linux Kernel list; Michal Simek; John > Linn; John Williams > Subject: Re: Xilinx SYSACE driver and 8-bit attachment > > On Wed, Oct 7, 2009 at 8:42 AM, John Linn wrote: > >> -----Original Message----- > >> From: John Linn > >> Sent: Wednesday, October 07, 2009 8:24 AM > >> To: 'Grant Likely'; John Williams > >> Cc: Linux Kernel list; Michal Simek; David DeBonis; Stephen Neuendorffer; devicetree-discuss > >> Subject: RE: Xilinx SYSACE driver and 8-bit attachment > >> > >> I'll look to see if something has changed. ?It's not clear to me if it has ever been right. > >> > >> It look like we normally use 16 bit mode as that's how BSB generates the system by default. > >> > >> Thanks, > >> John > >> > >> > -----Original Message----- > >> > From: glikely@secretlab.ca [mailto:glikely@secretlab.ca] On Behalf Of Grant Likely > >> > Sent: Wednesday, October 07, 2009 7:35 AM > >> > To: John Williams > >> > Cc: Linux Kernel list; Michal Simek; John Linn; David DeBonis; Stephen Neuendorffer; devicetree- > >> > discuss > >> > Subject: Re: Xilinx SYSACE driver and 8-bit attachment > >> > > >> > [Added devicetree-discuss to cc: list] > >> > > >> > On Wed, Oct 7, 2009 at 1:13 AM, John Williams > >> > wrote: > >> > > Hi Grant (it's your driver :) and David D ( and your DTS generator :) > >> > [...] > >> > > if (of_find_property(op->node, "8-bit", NULL)) > >> > [...] > >> > > doesn't match the properties generated by Xilinx's device tree generator: > >> > [...] > >> > > ??????????????????????? xlnx,mem-width = <0x8>; > > > > Do you know if the 8 bit mode was ever tested with the "8-bit" property in the tree? > > > > I don't see anything in the device tree generator history to say we ever did that "8-bit", but > maybe I'm missing something. > > > > We are just generating the parameters from the h/w and the memory width is it. ?We can always put > something in there special, but it seems silly if it was never used anyway. > > Don't forget that Virtex and Microblaze are not the only users of this > driver. There is a AMCC 440 board which uses the sysace as a CF > adapter. 8-bit was definitely tested and is in use. In this case, I'm pretty sure this tag was never automatically generated by the DTS generator. Personally, I think it's bad practice to always assume that the device tree generator should be modified to match what a Linux driver is expecting, however given the precedence in this case, I agree that it might be reasonable to put a special case in to generate this. Steve This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/