Re: eSCI patch [was Re: Freescale unified driver]

[Ilija Koco <ilijak at siva dot com dot mk>]

Andrew Lunn wrote:
>> I made the #define as you suggested and it seem to work, but now we have
>> another situation. eSCI driver is being silently discarded allthough
>> selected by user. In previous situation user had a kind of warning that
>> "something is missing" which was somewhat true: including driver is of
>> little use without including at least 1 device since there isn't a
>> (regular) way to access it.
>>     
>
> In CDL you can have a requires statement that at least one device is
> enable. Hopefully there will then be a conflict to indicate to the
> user something is wrong. The danger is the inferance engine will solve
> the conflict by simply enabling one of the devices. The one it picks
> may however not be the one the user wants. When using ecosconfig this
> will be clear, since it prints what inferences it has made. I don't
> use the configtool, so i don't know if it throws up a dialog box
> showing its inferences? 
>
>   
This is it - I should have thought of this :-(
As Peter noted configtool is a friendly tool. In my case it created a
dialog with 1 selected serial channel (out of 4 ored - below I have a
note for configtool developers).
Now I'll make usual tests and send a patch,

Regards
Ilija

P.S. Note to configtool developers:
suppose we have following expression in some component:
...
requires (A || B || C)
...

configtool will open dialog with an offer to resolve the conflict by
selecting 1 choice possibly A. Other choices don't appear in the dialog.
For user's convenience, could you consider offering all choices (for
instance 1 selected and other's unselected)?