Message ID | 20211124220057.15763-1-digetx@gmail.com |
---|---|
Headers | show |
Series | Support HDMI audio on NVIDIA Tegra20 | expand |
25.11.2021 01:00, Dmitry Osipenko пишет: > Add S/PDIF node to Tegra20 device-tree. It's needed for enabling HDMI > audio support. > > Signed-off-by: Dmitry Osipenko <digetx@gmail.com> > --- > arch/arm/boot/dts/tegra20.dtsi | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi > index 63c2c2f8c0ce..799da7dc929b 100644 > --- a/arch/arm/boot/dts/tegra20.dtsi > +++ b/arch/arm/boot/dts/tegra20.dtsi > @@ -197,6 +197,7 @@ hdmi@54280000 { > reset-names = "hdmi"; > power-domains = <&pd_core>; > operating-points-v2 = <&hdmi_dvfs_opp_table>; > + #sound-dai-cells = <0>; > status = "disabled"; > }; > > @@ -396,6 +397,23 @@ tegra_ac97: ac97@70002000 { > status = "disabled"; > }; > > + tegra_spdif: spdif@70002400 { > + compatible = "nvidia,tegra20-spdif"; > + reg = <0x70002400 0x200>; > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&tegra_car TEGRA20_CLK_SPDIF_OUT>, > + <&tegra_car TEGRA20_CLK_SPDIF_IN>; > + clock-names = "spdif_out", "spdif_in"; > + resets = <&tegra_car 10>; > + dmas = <&apbdma 3>, <&apbdma 3>; > + dma-names = "rx", "tx"; > + #sound-dai-cells = <0>; > + status = "disabled"; > + > + assigned-clocks = <&tegra_car TEGRA20_CLK_SPDIF_OUT>; > + assigned-clock-parents = <&tegra_car TEGRA20_CLK_PLL_A_OUT0>; > + }; > + > tegra_i2s1: i2s@70002800 { > compatible = "nvidia,tegra20-i2s"; > reg = <0x70002800 0x200>; > @Thierry, this patch is made on top of [1]. [1] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=271954
On Thu, Nov 25, 2021 at 01:00:44AM +0300, Dmitry Osipenko wrote:
> Program FIFO trigger level properly to fix x4 accelerated playback.
Fixes like this should really go before any new stuff so they can be
sent as fixes and backported.
25.11.2021 15:02, Mark Brown пишет: > On Thu, Nov 25, 2021 at 01:00:44AM +0300, Dmitry Osipenko wrote: >> Program FIFO trigger level properly to fix x4 accelerated playback. > > Fixes like this should really go before any new stuff so they can be > sent as fixes and backported. > This driver never worked before this patchset, hence there is nothing to backport, this is explained in the cover letter. But in general you're correct.
On Thu, Nov 25, 2021 at 03:04:35PM +0300, Dmitry Osipenko wrote: > 25.11.2021 15:02, Mark Brown пишет: > > On Thu, Nov 25, 2021 at 01:00:44AM +0300, Dmitry Osipenko wrote: > >> Program FIFO trigger level properly to fix x4 accelerated playback. > > Fixes like this should really go before any new stuff so they can be > > sent as fixes and backported. > This driver never worked before this patchset, hence there is nothing to > backport, this is explained in the cover letter. But in general you're > correct. That's not going to stop the stable people backporting things, and I'd guess it might've worked at some point on some systems - I'm not seeing anything that jumps out as making the driver completely unworkable in your patches.
25.11.2021 15:28, Mark Brown пишет: > On Thu, Nov 25, 2021 at 03:04:35PM +0300, Dmitry Osipenko wrote: >> 25.11.2021 15:02, Mark Brown пишет: >>> On Thu, Nov 25, 2021 at 01:00:44AM +0300, Dmitry Osipenko wrote: >>>> Program FIFO trigger level properly to fix x4 accelerated playback. > >>> Fixes like this should really go before any new stuff so they can be >>> sent as fixes and backported. > >> This driver never worked before this patchset, hence there is nothing to >> backport, this is explained in the cover letter. But in general you're >> correct. > > That's not going to stop the stable people backporting things, and I'd > guess it might've worked at some point on some systems - I'm not seeing > anything that jumps out as making the driver completely unworkable in > your patches. > I can change commit message with the "fix" word removed, this should prevent patch from backporting. This driver never worked in mainline because S/PDIF device was never created, thus driver was never bound. Driver doesn't work properly without this patch. Nobody used this driver as-is before this patchset.
On Thu, Nov 25, 2021 at 03:53:52PM +0300, Dmitry Osipenko wrote: > 25.11.2021 15:28, Mark Brown пишет: > > On Thu, Nov 25, 2021 at 03:04:35PM +0300, Dmitry Osipenko wrote: > >> This driver never worked before this patchset, hence there is nothing to > >> backport, this is explained in the cover letter. But in general you're > >> correct. > > That's not going to stop the stable people backporting things, and I'd > > guess it might've worked at some point on some systems - I'm not seeing > > anything that jumps out as making the driver completely unworkable in > > your patches. > I can change commit message with the "fix" word removed, this should > prevent patch from backporting. I wouldn't count on it TBH. In any case, definitely no need to resend for this alone. > This driver never worked in mainline because S/PDIF device was never > created, thus driver was never bound. Driver doesn't work properly > without this patch. Nobody used this driver as-is before this patchset. Someone might've been using it with an out of tree board file, I guess on an older stable at this point.
25.11.2021 16:18, Mark Brown пишет: > On Thu, Nov 25, 2021 at 03:53:52PM +0300, Dmitry Osipenko wrote: >> 25.11.2021 15:28, Mark Brown пишет: >>> On Thu, Nov 25, 2021 at 03:04:35PM +0300, Dmitry Osipenko wrote: > >>>> This driver never worked before this patchset, hence there is nothing to >>>> backport, this is explained in the cover letter. But in general you're >>>> correct. > >>> That's not going to stop the stable people backporting things, and I'd >>> guess it might've worked at some point on some systems - I'm not seeing >>> anything that jumps out as making the driver completely unworkable in >>> your patches. > >> I can change commit message with the "fix" word removed, this should >> prevent patch from backporting. > > I wouldn't count on it TBH. In any case, definitely no need to resend > for this alone. Alright, I'll keep this in mind for a potential v2. I guess Rob may ask to remove the assigned-clocks from S/PDIF DT binding because I just found that there is no needed to specify that property explicitly anymore. >> This driver never worked in mainline because S/PDIF device was never >> created, thus driver was never bound. Driver doesn't work properly >> without this patch. Nobody used this driver as-is before this patchset. > > Someone might've been using it with an out of tree board file, I guess > on an older stable at this point. > I'm very doubtful. Still, this patch could be easily backported because all code refactoring changes that potentially may cause merge conflicts are made after this patch. Ideally, if we really needed to backport this patch, then it should've been one of the first patches as you suggested.