From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752982Ab1AZPRi (ORCPT ); Wed, 26 Jan 2011 10:17:38 -0500 Received: from relais.videotron.ca ([24.201.245.36]:51200 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751435Ab1AZPRg (ORCPT ); Wed, 26 Jan 2011 10:17:36 -0500 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: TEXT/PLAIN; charset=US-ASCII Date: Wed, 26 Jan 2011 10:17:35 -0500 (EST) From: Nicolas Pitre X-X-Sender: nico@xanadu.home To: Thomas Chou Cc: Grant Likely , David Miller , lkml , nios2-dev@sopc.et.ntust.edu.tw, devicetree-discuss@lists.ozlabs.org, netdev@vger.kernel.org Subject: Re: [PATCH v4] smc91x: add devicetree support In-reply-to: <1296019325-17801-1-git-send-email-thomas@wytron.com.tw> Message-id: References: <20110125.194532.71125517.davem@davemloft.net> <1296019325-17801-1-git-send-email-thomas@wytron.com.tw> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Jan 2011, Thomas Chou wrote: > Signed-off-by: Thomas Chou > --- > v2 specify part numbers in compat as Grant suggested. > v3 more specific part name. > v4 include match table only for OF as David suggested. The smc91x driver relies on many parameters which are platform specific, such as the bus width capabilities, register spacing due to special bus wiring, interrupt signal level, LED configuration, whether or not to configure the chip with a wait state, etc. Will the device tree support take care of those things? Nicolas From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Pitre Subject: Re: [PATCH v4] smc91x: add devicetree support Date: Wed, 26 Jan 2011 10:17:35 -0500 (EST) Message-ID: References: <20110125.194532.71125517.davem@davemloft.net> <1296019325-17801-1-git-send-email-thomas@wytron.com.tw> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, lkml , David Miller To: Thomas Chou Return-path: In-reply-to: <1296019325-17801-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: netdev.vger.kernel.org On Wed, 26 Jan 2011, Thomas Chou wrote: > Signed-off-by: Thomas Chou > --- > v2 specify part numbers in compat as Grant suggested. > v3 more specific part name. > v4 include match table only for OF as David suggested. The smc91x driver relies on many parameters which are platform specific, such as the bus width capabilities, register spacing due to special bus wiring, interrupt signal level, LED configuration, whether or not to configure the chip with a wait state, etc. Will the device tree support take care of those things? Nicolas