Hello Bergman,
Thanks for your help and time. Also I have seen that sometimes we use
i2c0: i2c@44e0b000 {
}
and Sometimes
i2c@44e0b000
Why is that? What is the purpose of adding a i2c0: infront of the i2c
entry. that too in the same file.
Regards,
ryan
On Fri, Jan 29, 2016 at 2:19 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote:
> On Friday 29 January 2016 14:13:20 Ryan wrote:
>> Hello,
>>
>> I am confused about the "status" variables on a device tree. What is
>> the meaning of
>> status="okay", status="enabled", status="disabled".
>>
>> the function: __of_device_is_available returns 1 if the entry itself
>> is not there.
>>
>> Why is this?
>>
>> Thanks for your time.
>
> On status="disabled" is defined to have an effect and will prevent
> the device from being used. Any other value or an absent status
> property is interpreted as a working device.
>
> The common way this is used is that a soc-specific .dtsi file lists
> all devices that are present within the soc, but marks the ones as
> disabled that are not always usable because they depend on a external
> connection (e.g. a uart only makes sense if it talks to something,
> while a timer device is always usable). A board specific file then
> does not need to define the entire device but just override the
> status as "okay".
>
> Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
