From owner-freebsd-arm@FreeBSD.ORG Sun Feb 2 19:31:53 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA0ACA01 for ; Sun, 2 Feb 2014 19:31:53 +0000 (UTC) Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A240C16FF for ; Sun, 2 Feb 2014 19:31:53 +0000 (UTC) Received: by mail-ig0-f176.google.com with SMTP id j1so2890961iga.3 for ; Sun, 02 Feb 2014 11:31:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=b/fLLpZbnCqFk7lDbqovYscDeTgrZOWazSUGKD+ITwU=; b=Tewi3IUWQCHVM59lfUE4h9DwBFn3MNd0h12Qh0+oJz4+PWneGC30T3sY6mSyOg0Szf dn6J8zZQZDcAa/e4eBSza8Ppkkx6MS8rhpwzA5NgK4XZYCtUJADtC5MdF6W0Vec2Bh4i yHw4/FYbkUsTbd0ryhkfRXSAor4PDiHbgYQ0Er+10yeUPNdbXjK+XZxejzH/b9Qfv4yR wfETa+qxrIEuUhF6l6FzsbtqY6hOXokjW3eA4vk7j1V7wuY2h+HVAJiF9fFrc8MhWaU2 uPxa1fsZ2JGl6f3eDYlw5rjBrXRKLQt+fXyMadRIGdfnCi3fl7cyFOMXYc0elmg1aVVC dWzw== X-Gm-Message-State: ALoCoQm6d88l5JSVj8+gFMO/bcgStr/Ax/4G0g1/V0YfZVf/uJ8kc1ky2lHSscDOk8PpxixakrNg X-Received: by 10.50.73.136 with SMTP id l8mr8817620igv.7.1391369506080; Sun, 02 Feb 2014 11:31:46 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id ft2sm22263041igb.5.2014.02.02.11.31.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Feb 2014 11:31:45 -0800 (PST) Sender: Warner Losh Subject: Re: status = "disabled" Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=iso-8859-1 From: Warner Losh In-Reply-To: <52EE622C.9010004@freebsd.org> Date: Sun, 2 Feb 2014 12:31:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <726dc97ccd1f44b3ba9d7bee3eeff08a@e15be-01.zdv.Uni-Mainz.DE> <52EE622C.9010004@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1085) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 19:31:53 -0000 On Feb 2, 2014, at 8:20 AM, Nathan Whitehorn wrote: > On 02/02/14 05:55, Wei=DF, J=FCrgen wrote: >>=20 >> it seems your recent changes (261351) discarded a call to = fdt_is_enabled >> for devices on simplebus. So 'status =3D "disabled" ' does not work >> anymore in arm dts. >>=20 > That's actually required to make some hardware work ("disabled" may = just mean the clock is turned off and needs to be turned back on, which = means you absolutely do want that device probed). The device drivers = themselves, not the bus, should be checking this property and = interpreting it. If this has actually broken hardware, we could add a = temporary #ifdef __arm__ check to the simplebus tree-walker while the = relevant drivers get fixed up. I suspect that it is going to be a cooperation between the bus and the = driver. Eg, we want them probed, and their resources allocated, but we = otherwise don't want the driver to interact with the hardware. So a = serial driver wouldn't create /dev/ttyUx nodes, a network driver = wouldn't try to attach an if_net, etc. Also, we need an interface, = eventually, that will allow us to turn them back on, but that can be = problematic since one of the resources the drivers use is hardware pins, = which are multiplexed with other drivers... Warner