mfd: madera: Add register definitions for accessory detect

2018-08-16T09:14:05+00:00

Add some register definitions for accessory detection, used by the extcon driver. Signed-off-by: Richard Fitzgerald Signed-off-by: Lee Jones

mfd: madera: Add common support for Cirrus Logic Madera codecs

2018-06-05T10:14:56+00:00

This adds the generic core support for Cirrus Logic "Madera" class codecs. These are complex audio codec SoCs with a variety of digital and analogue I/O, onboard audio processing and DSPs, and other features. These codecs are all based off a common set of hardware IP so can be supported by a core of common code (with a few minor device-to-device variations). Signed-off-by: Charles Keepax Signed-off-by: Nikesh Oswal Signed-off-by: Richard Fitzgerald Signed-off-by: Lee Jones

mfd: madera: Add register definitions for Cirrus Logic Madera codecs

2018-06-05T10:14:32+00:00

This patch adds a header file of register definitions for Cirrus Logic "Madera" class codecs. These codecs are all based off a common set of hardware IP so have a common register map (with a few minor device-to-device variations). The registers.h file is tool-generated directly from the hardware design but has been manually stripped down to reduce size (full register map is >44000 lines). All names are kept the same as datasheet names so that they can be cross-referenced between source and datasheet without confusion. The register map layout is kept fully-defined rather than factored into macros and/or block-indexing code. The major reasons for this are: - #1 is that it makes the source highly greppable, which is important. "What does the driver do with register bits XYZ" or "Where does it use register bits XYZ" are commonly types of questions. These can be quickly answered by a grep. Squashing definitions into generator macros or block- indexing code is a way of defeating grep. - most of the register definitions are used in tables, so a constant value is required. Using generator macros make the table definition clunky and obscure. - the code is clearer when it's there in the source exactly what register and field it is using - it is easier to diff the register map of a new (unsupported) codec against what is already supported and merge in differences - it makes the register map available in source for maintenance/debugging instead of having to refer back to the datasheet for a register map Signed-off-by: Richard Fitzgerald Signed-off-by: Lee Jones

kernel/linux.git/include/linux/mfd/madera, branch v4.19.170

mfd: madera: Add register definitions for accessory detect

mfd: madera: Add common support for Cirrus Logic Madera codecs

mfd: madera: Add register definitions for Cirrus Logic Madera codecs