While I do see benefit of using enum and (thus only one API is needed), what Morgaine pointed

out is also a good point. I think I will stick to current two individual APIs w/o enum but am

open if any strong thought of using the enum. Thanks.


From: Morgaine [mailto:morgaine.dinova(a)googlemail.com]
Sent: Wednesday, July 27, 2016 9:36 AM
To: devel(a)lists.zephyrproject.org
Subject: [devel] Re: Re: Re: Re: Re: [RFC] Provide a generic interface for getting the SOC ID and version

how about one API which takes an enumerated type to select which data to retrieve?

That would create an artificial interdependency between the two unrelated types of data via their shared access method. Someone would have to maintain the enumerated type, and while that's not hard, it's an unnecessary burden on maintainers, a burden that provides no payback. It's more detail for users to figure out as well.
Extra complexity isn't necessarily bad, it just depends on how much you gain from the extra pain. In this instance though, there was no gain described, and I can't yet see any benefit that this would bring.