On 04/23/2012 11:40 AM, John Crispin wrote: > If a non existent mux group is referenced inside a devicetree, we see no > error. > > This patch adds the same type of error message that pinconf_map_to_setting() > gives when the pin/group is unknown. > > Signed-off-by: John Crispin <[email protected]> > Cc: Stephen Warren <[email protected]>
There are some other cases where more error messages would be useful, such as invalid function name, invalid config options etc. I was planning on going through the code and adding these since some of these are hitting me on a new board I'm adding to mainline. Are you planning to add more of these messages, or should I go ahead with that? I wonder if the message would be more useful if it said something like "invalid group %s for function %s" - that would give a little more information for the user to track down the incorrect entry, since that group name may be valid in general, just not for the function being converted. BTW, the "Cc" you added to the commit description doesn't appear to be happening; I'm only receiving this message through the list. _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
