On Mon, Jan 18, 2021 at 02:31:35AM +0300, Dmitry Osipenko wrote:
> 15.01.2021 18:22, Thierry Reding пишет:
> ...
> >> static int hda_tegra_first_init(struct azx *chip, struct platform_device *pdev)
> >> {
> >> struct hda_tegra *hda = container_of(chip, struct hda_tegra, chip);
> >> @@ -495,7 +441,11 @@ static int hda_tegra_probe(struct platform_device *pdev)
> >> return err;
> >> }
> >>
> >> - err = hda_tegra_init_clk(hda);
> >> + hda->clocks[hda->nclocks++].id = "hda";
> >> + hda->clocks[hda->nclocks++].id = "hda2hdmi";
> >> + hda->clocks[hda->nclocks++].id = "hda2codec_2x";
> >
> > Originally the code did this in this order: "hda", "hda2codec_2x" and
> > "hda2hdmi". I don't expect the exact order to be very relevant, but was
> > there any particular reason to change it?
>
> The reason was "to make code look nicer". This was a conscious decision
> since indeed the clocks order shouldn't matter for this driver.
Yeah, it's probably fine. In case this ends up causing trouble after all
we can always change the order back.
Thierry
Attachment:
signature.asc
Description: PGP signature
