spi: pxa2xx: Add SSC2 and SSPSP2 SSP registers
PATCH v2 1/1 spi: pxa2xx: Add SSC2 and SSPSP2 SSP registers
Update list of SSP registers with SSC2 and SSPSP2. These registers are utilized by LPT/WPT AudioDSP architecture.
While SSC2 shares the same offset (0x40) as SSACDD, description of this register for SSP device present on mentioned AudioDSP is different so define separate constant to avoid any ambiguity.
--- include/linux/pxa2xx_ssp.h | 4 ++++ 1 file changed, 4 insertions(+)
include/linux/pxa2xx_ssp.h +4 -0
@@ -186,6 +186,10 @@#define SSIRF 0x48/* RX FIFO trigger level */ #define SSIRF_RxThresh (x) ((x) - 1) +/* LPT/WPT SSP */ +#define SSCR2 (0x40)/* SSP Command / Status 2 */ +#define SSPSP2 (0x44)/* SSP Programmable Serial Protocol 2 */ +enum pxa_ssp_type {SSP_UNDEFINED =0 , PXA25x_SSP,/* pxa 210, 250, 255, 26x */
Signature · 1 line
2.17.1
Quoted 10 lines · Cezary Rojewski
Update list of SSP registers with SSC2 and SSPSP2. These registers are utilized by LPT/WPT AudioDSP architecture.
While SSC2 shares the same offset (
0x40) as SSACDD, description of this register for SSP device present on mentioned AudioDSP is different so define separate constant to avoid any ambiguity.Cc Andy Shevchenko <[email protected]>Signed-off-by Cezary Rojewski <[email protected]>Reviewed-by Andy Shevchenko <[email protected]>
Side note for the future: When you put a tag, you may remove Cc of the same person (git-send-email will add Cc based on the tag).
Signature · 2 lines
With Best Regards, Andy Shevchenko
Mark Brown
maintainerQuoted 6 lines · Cezary Rojewski
Update list of SSP registers with SSC2 and SSPSP2. These registers are utilized by LPT/WPT AudioDSP architecture.
While SSC2 shares the same offset (
0x40) as SSACDD, description of this register for SSP device present on mentioned AudioDSP is different so define separate constant to avoid any ambiguity.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: pxa2xx: Add SSC2 and SSPSP2 SSP registers
commit: a2bee00cccf4f2a80412d38328b92f448fd66935
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark