Skip to contentSkip to conversation

ASoC: rt1015: fix i2c communication error

PATCH In review [email protected] 2 participants 3 messages Feb 22, 2021

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/2 ASoC: rt1015: fix i2c communication error

From: Jack Yu <[email protected]>

Remove 0x100 cache re-sync to solve i2c communication error.

---
 sound/soc/codecs/rt1015.c | 1 +
 1 file changed, 1 insertion(+)
sound/soc/codecs/rt1015.c +1 -0
index 37b5795b00d1..90767490af82 100644
@@ -209,6 +209,7 @@ static bool rt1015_volatile_register(struct device *dev, unsigned int reg)
 	case RT1015_VENDOR_ID:
 	case RT1015_DEVICE_ID:
 	case RT1015_PRO_ALT:
+	case RT1015_MAN_I2C:
 	case RT1015_DAC3:
 	case RT1015_VBAT_TEST_OUT1:
 	case RT1015_VBAT_TEST_OUT2:
Signature · 1 line
2.29.0
#1 lore raw

PATCH 2/2 ASoC: rt1015: enable BCLK detection after calibration

From: Jack Yu <[email protected]>

Enable BCLK detection after calibration.

---
 sound/soc/codecs/rt1015.c | 1 +
 1 file changed, 1 insertion(+)
sound/soc/codecs/rt1015.c +1 -0
index 90767490af82..844e4079d176 100644
@@ -514,6 +514,7 @@ static void rt1015_calibrate(struct rt1015_priv *rt1015)
 	msleep(300);
 	regmap_write(regmap, RT1015_PWR_STATE_CTRL, 0x0008);
 	regmap_write(regmap, RT1015_SYS_RST1, 0x05F5);
+	regmap_write(regmap, RT1015_CLK_DET, 0x8000);
 
 	regcache_cache_bypass(regmap, false);
 	regcache_mark_dirty(regmap);
Signature · 1 line
2.29.0
maintainer
#2 lore raw
In reply to [email protected]
Quoted 1 line · On Mon, 22 Feb 2021 17:00:56 +0800, [email protected] wrote:

Remove 0x100 cache re-sync to solve i2c communication error.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: rt1015: fix i2c communication error

      commit: 7fb08871c38ba9e871d20d64f3a27409baf7b754
[2/2] ASoC: rt1015: enable BCLK detection after calibration
      commit: 2979ef760e73e2a1a34cd4da5d2c78371dfe1028

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