Messages in this thread | | | Date | Thu, 10 May 2012 15:45:43 +0530 | Subject | Re: [PATCH 3/7] mmc: dw_mmc: add device tree support | From | Thomas Abraham <> |
| |
Hi Olof,
On 2 May 2012 23:37, Olof Johansson <olof@lixom.net> wrote: > Hi,
[...]
>> +# Slots: The slot specific information are contained within child-nodes with >> + each child-node representing a supported slot. There should be atleast one >> + child node representing a card slot. The name of the slot child node should >> + be 'slot{n}' where n is the unique number of the slot connnected to the >> + controller. The following are optional properties which can be included in >> + the slot child node. > > Since we're talking slots / cards on a bus, I think the addressing > model would be useful here. So in the main controller node: > #address-cells = <1>; > #size-cells = <0>; > > And then each slot would need a reg property and possibly unit address: > > slot { > reg = <0>; > ... > }; > > (unit addresses on the slots are only needed if they can't be > disambiguated by name, so not needed if you only have one slot). >
Is the addressing model as described above needed in this case? The address for a slot is not used by the controller driver code and is just a virtual number. It would be sufficient to represent the nodes representing the slots with a unique name.
Thanks, Thomas. -- 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/
| |