StarFive Tech Linux Kernel for VisionFive (JH7110) boards (mirror) https://git.radix-linux.su/starfive-tech/linux.git/atom?h=JH7110_VisionFive2_multi_rtos 2024-03-05T07:18:30+00:00 2024-03-05T07:18:30+00:00 Walker Chen walker.chen@starfivetech.com 2023-06-20T07:57:53+00:00 urn:sha1:fc02029502a5eada84c3aa254bf1fcae6debf203 Add pdm driver support for the StarFive JH7110 SoC. Signed-off-by: Walker Chen <walker.chen@starfivetech.com> 2024-03-05T07:18:29+00:00 Xingyu Wu xingyu.wu@starfivetech.com 2023-06-15T03:32:50+00:00 urn:sha1:d9d4dbd4c56e4be328962588b632fcbd02d547ab Add SPDIF and SPDIF-PCM driver for StarFive JH7110. Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> 2024-03-05T07:18:29+00:00 Xingyu Wu xingyu.wu@starfivetech.com 2023-06-16T08:27:46+00:00 urn:sha1:f1856591020dd41413a2b02f7ed5fb3de67146ee Add AC108 Codec driver and AC101 driver for AC10x. Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> 2024-03-05T07:18:29+00:00 Walker Chen walker.chen@starfivetech.com 2023-06-12T13:29:00+00:00 urn:sha1:95c85c06eb21ee26bfe9c8b34c472f49b03aaf8a Configure WM8960 to be used for JH7110 TDM & I2S. Signed-off-by: Walker Chen <walker.chen@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> 2024-03-05T07:18:27+00:00 Xingyu Wu xingyu.wu@starfivetech.com 2023-10-17T09:22:52+00:00 urn:sha1:2fef0872da3893e4646d19245fd4463c8128b078 Add JH7110 I2S RX master support, so the PDM can work on JH7110 EVB board. Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> 2024-03-05T07:18:27+00:00 Xingyu Wu xingyu.wu@starfivetech.com 2024-02-21T02:23:48+00:00 urn:sha1:29ebe44f04a92b477aa25a473c1a95788e4eb98c JH7110 need to use a DT specific function to get the platform data, otherwise, it fails in probe(). Fixes: 9c97790a07dc ("ASoC: dwc: Fix non-DT instantiation") Signed-off-by: Xingyu Wu <xingyu.wu@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> 2024-03-05T07:18:26+00:00 Uwe Kleine-König u.kleine-koenig@pengutronix.de 2023-10-13T22:19:49+00:00 urn:sha1:2a8e68924fface3e1b3d61ee16fddd7254576e48 The .remove() callback for a platform driver returns an int which makes many driver authors wrongly assume it's possible to do error handling by returning an error code. However the value returned is ignored (apart from emitting a warning) and this typically results in resource leaks. To improve here there is a quest to make the remove callback return void. In the first step of this quest all drivers are converted to .remove_new(), which already returns void. Eventually after all drivers are converted, .remove_new() will be renamed to .remove(). Trivially convert this driver from always returning zero in the remove callback to the void returning variant. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Link: https://lore.kernel.org/r/20231013221945.1489203-12-u.kleine-koenig@pengutronix.de Signed-off-by: Mark Brown <broonie@kernel.org> 2024-03-05T07:18:26+00:00 Mark Brown broonie@kernel.org 2023-09-11T22:48:39+00:00 urn:sha1:498f959997a4a856fd6e1eeed014dc68682556e1 For some reason the JH7110 PWM DAC driver made it through build testing in spite of not being updated for the move of probe() to the ops struct. Make the required update. Signed-off-by: Mark Brown <broonie@kernel.org> 2024-03-05T07:18:26+00:00 Hal Feng hal.feng@starfivetech.com 2023-08-14T08:06:17+00:00 urn:sha1:fec6ae6a3454520fcb151174fbbb6c975d184a14 Add PWM-DAC driver support for the StarFive JH7110 SoC. Reviewed-by: Walker Chen <walker.chen@starfivetech.com> Signed-off-by: Hal Feng <hal.feng@starfivetech.com> Link: https://lore.kernel.org/r/20230814080618.10036-3-hal.feng@starfivetech.com Signed-off-by: Mark Brown <broonie@kernel.org> 2024-03-01T12:34:52+00:00 Alexander Tsoy alexander@tsoy.me 2024-02-01T11:53:08+00:00 urn:sha1:ffd63f243735aebc092f1fee9fc1f9d8ce20bfb4 [ Upstream commit eaa1b01fe709d6a236a9cec74813e0400601fd23 ] For devices with multiple clock sources connected to a selector, we need to check what a clock selector control request has returned. This is needed to ensure that a requested clock source is indeed selected and for autoclock feature to work. For devices with single clock source connected, if we get an error there is nothing else we can do about it. We can't skip clock selector setup as it is required by some devices. So lets just ignore error in this case. This should fix various buggy Mackie devices: [ 649.109785] usb 1-1.3: parse_audio_format_rates_v2v3(): unable to find clock source (clock -32) [ 649.111946] usb 1-1.3: parse_audio_format_rates_v2v3(): unable to find clock source (clock -32) [ 649.113822] usb 1-1.3: parse_audio_format_rates_v2v3(): unable to find clock source (clock -32) There is also interesting info from the Windows documentation [1] (this is probably why manufacturers dont't even test this feature): "The USB Audio 2.0 driver doesn't support clock selection. The driver uses the Clock Source Entity, which is selected by default and never issues a Clock Selector Control SET CUR request." Link: https://learn.microsoft.com/en-us/windows-hardware/drivers/audio/usb-2-0-audio-drivers [1] Link: https://bugzilla.kernel.org/show_bug.cgi?id=217314 Link: https://bugzilla.kernel.org/show_bug.cgi?id=218175 Link: https://bugzilla.kernel.org/show_bug.cgi?id=218342 Signed-off-by: Alexander Tsoy <alexander@tsoy.me> Link: https://lore.kernel.org/r/20240201115308.17838-1-alexander@tsoy.me Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Sasha Levin <sashal@kernel.org>