Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751180Ab3HTNTK (ORCPT ); Tue, 20 Aug 2013 09:19:10 -0400 Received: from mail-ve0-f179.google.com ([209.85.128.179]:54304 "EHLO mail-ve0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751021Ab3HTNTI (ORCPT ); Tue, 20 Aug 2013 09:19:08 -0400 MIME-Version: 1.0 In-Reply-To: <20130819160130.GD30073@sirena.org.uk> References: <20130816224654.GV30073@sirena.org.uk> <20130819160130.GD30073@sirena.org.uk> Date: Tue, 20 Aug 2013 21:19:07 +0800 Message-ID: Subject: Re: Non-enumerable devices on USB and other enumerable buses From: Ming Lei To: Mark Brown Cc: Alan Stern , Greg Kroah-Hartman , Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Felipe Balbi , Grant Likely , "devicetree@vger.kernel.org" , linux-usb , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1450 Lines: 34 On Tue, Aug 20, 2013 at 12:01 AM, Mark Brown wrote: > On Mon, Aug 19, 2013 at 08:17:53PM +0800, Ming Lei wrote: >> On Sat, Aug 17, 2013 at 9:29 AM, Alan Stern wrote: > >> > Aong those lines, I would like to point out that the device concept >> > embodied in the kernel's data structures can be pretty thin. For >> > example, it might be little more than a port number or bus address. > >> Maybe the principle behind drivers/usb/core/usb-acpi.c is helpful >> for the problem, and DT may refer to ACPI to describe on-board >> USB devices, and the way to retrieve platform data too. > > I can't parse this at all well - why would DT want to refer to ACPI, do > you mean people may wish to look at the code as an example? As Grant I mean usb-acpi provides one approach to retrieve platform data for USB device during device enumeration, and the idea might be helpful for you to implement similar things based on DT. > noted DT already has some mechanisms for enumerable buses which looking > at the code appears to be broadly what that's doing. If the mechanism is ready now, so looks you might post code for review and discussion? Thanks, -- Ming Lei -- 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/