[...] > > > > > > One option to achieve a similar degree of flexibility by using an array > > > OF property (instead of several u32 properties) would be to agree on a > > > convention based on magic values, i.e. below DT one-liner could be an > > > example of providing solely the "fixed-emmc-driver-type-hs200" value > > > (based on the agreement that 0xFF values are discarded by the driver): > > > > > > fixed-emmc-driver-type = <0xFF 0x1 0xFF>; > > > > I don't understand why you have 3 values instead of 2. > > Because he sketches maximum flexibility here. Have a non-HS (default) > value, one for HS200, and one for HS400: > > fixed-emmc-driver-type = <[default] [HS200] [HS400]>; > > > I would just use -1 if you want to ignore an entry. If that's the common > > '-1' sounds good to me, too. > > > case, then I'd stick with what you originally proposed. If rare, then I > > think an array is the better route. > > What I have seen so far: setting drive strength alone is more on the > rare side. Setting specific values for default and HS200/400 seems even > more rare to me. With this patchset, it is the first time I hear about > it. > > Yet, my experience might be a bit limited, maybe others (Hi Ulf! ;)) can add > their views, too? My experience in this field is quite limited. No input from me, sorry. Kind regards Uffe
