On Sat, Nov 26, 2016 at 10:18:38AM +0100, Robert Jarzmik wrote: > >> >> +#define WM9705_VENDOR_ID 0x574d4c05 > >> >> +#define WM9712_VENDOR_ID 0x574d4c12 > >> >> +#define WM9713_VENDOR_ID 0x574d4c13 > >> >> +#define WM97xx_VENDOR_ID_MASK 0xffffffff > >> > These are probably better represented as enums. > >> These are ids, just as devicetree ids, or PCI ids, I don't think an enum will > >> fit. > > That's fine. We can use enums to simply group items of a similar > > type. Representing these as enums would only serve to benefit code > > cleanliness. What makes you think they won't fit? That would be like having all PCI or USB identifiers in an enum, it's doable but it means having one big table that all drivers need to modify. > >> >> +static int wm97xx_ac97_probe(struct ac97_codec_device *adev) > >> As for the "sound specific part", it's because AC97 bus is mainly used in sound > >> oriented drivers, but still the codec IPs provide more than just sound, as the > >> Wolfson codecs for instance. > > I'd like to get Mark Brown's opinion on this. I'm not sure what the question is, sorry.
Attachment:
signature.asc
Description: PGP signature
