Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Feb 2014 15:59:14 +0000
From:      =?iso-8859-1?B?V2Vp3ywgSvxyZ2Vu?= <weiss@uni-mainz.de>
To:        'Nathan Whitehorn' <nwhitehorn@freebsd.org>, "'freebsd-arm@freebsd.org'" <freebsd-arm@FreeBSD.org>
Subject:   RE: status = "disabled"
Message-ID:  <06235e983f8142fcb7f6f6c329a84b90@e15be-01.zdv.Uni-Mainz.DE>
In-Reply-To: <52EE622C.9010004@freebsd.org>
References:  <726dc97ccd1f44b3ba9d7bee3eeff08a@e15be-01.zdv.Uni-Mainz.DE> <52EE622C.9010004@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help


> -----Original Message-----
> From: Nathan Whitehorn [mailto:nwhitehorn@freebsd.org]
> Sent: Sunday, February 02, 2014 4:20 PM
> To: Wei=DF, J=FCrgen; freebsd-arm@freebsd.org
> Subject: Re: status =3D "disabled"
>=20
> On 02/02/14 05:55, Wei=DF, J=FCrgen wrote:
> > Hi,
> >
> > it seems your recent changes (261351) discarded a call to fdt_is_enable=
d
> > for devices on simplebus. So 'status =3D "disabled" ' does not work
> > anymore in arm dts.
> >
> > Regards
> >
> > Juergen Weiss
> >
> > Juergen Weiss      |Universitaet Mainz, Zentrum fuer Datenverarbeitung,
> > weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: +49(6131)=
39-26407
> >
> >
>=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.
> -Nathan


Thanks for the quick answer. Right know there seem to be zero device driver=
s
doing this. And there are quite a few fdts going from general (all devices =
on SOC)=20
to specific (devices usable on specific board), which use the status field
to disable a device (for example i.mx in general and wandboard specifically=
).
At least with the i.mx6 the unconnected sdhci devices lead to hangs during
boot.

Regards

Juergen Weiss

Juergen Weiss      |Universitaet Mainz, Zentrum fuer Datenverarbeitung,
weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: +49(6131)39-2=
6407




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?06235e983f8142fcb7f6f6c329a84b90>