mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH V3 1/3] arm64: dts: imx8mp: Add easrc node
Date: Fri, 1 Sep 2023 17:47:57 +0200	[thread overview]
Message-ID: <4ec813ef-aa0d-655e-3f78-7c669d72551c@denx.de> (raw)
In-Reply-To: <CAHCN7xJGGSaO949=u2W6jybdE5R1dE8ihdP9wSrCgk5+9=9H6g@mail.gmail.com>

On 9/1/23 13:02, Adam Ford wrote:
> On Thu, Aug 31, 2023 at 4:52 PM Marek Vasut <marex@denx.de> wrote:
>>
>> On 8/31/23 06:44, Adam Ford wrote:
>>> The i.MX8MP has an asynchronous sample rate converter which seems
>>> to be the same as what is available on the i.MX8M Nano.
>>>
>>> Signed-off-by: Adam Ford <aford173@gmail.com>
>>> ---
>>> V3:  No Change.  The dt-binding update was already accepted into the sound tree, so that patch
>>>        was dropped from the series
>>>
>>> V2:  No Change.
>>> diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> index 83d907294fbc..3167706d81e1 100644
>>> --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> @@ -1459,6 +1459,26 @@ sai7: sai@30c80000 {
>>>                                        interrupts = <GIC_SPI 111 IRQ_TYPE_LEVEL_HIGH>;
>>>                                        status = "disabled";
>>>                                };
>>> +
>>> +                             easrc: easrc@30c90000 {
>>> +                                     compatible = "fsl,imx8mp-easrc", "fsl,imx8mn-easrc";
>>> +                                     reg = <0x30c90000 0x10000>;
>>> +                                     interrupts = <GIC_SPI 122 IRQ_TYPE_LEVEL_HIGH>;
>>> +                                     clocks = <&audio_blk_ctrl IMX8MP_CLK_AUDIOMIX_ASRC_IPG>;
>>> +                                     clock-names = "mem";
>>> +                                     dmas = <&sdma2 16 23 0> , <&sdma2 17 23 0>,
>>> +                                            <&sdma2 18 23 0> , <&sdma2 19 23 0>,
>>> +                                            <&sdma2 20 23 0> , <&sdma2 21 23 0>,
>>> +                                            <&sdma2 22 23 0> , <&sdma2 23 23 0>;
>>> +                                     dma-names = "ctx0_rx", "ctx0_tx",
>>> +                                                 "ctx1_rx", "ctx1_tx",
>>> +                                                 "ctx2_rx", "ctx2_tx",
>>> +                                                 "ctx3_rx", "ctx3_tx";
>>> +                                     firmware-name = "imx/easrc/easrc-imx8mn.bin";
>>
>> Should the firmware name really be imx8mn or should it be imx8mp ?
> 
> The firmware blobs provided by NXP only has easrc-imx8mn.bin and would
> be concerned that having a different name might confuse people if they
> try to go look for it and they only find easrc-imx8mn.bin.  To me,
> this is no different than the SDMA driver using firmware called
> sdma-imx7d.bin

On the other hand, there is "fsl,imx8mp-easrc" compatible string -- to 
differentiate between IPs in case some difference between the IPs that 
cannot be predicted so far is found later on.

>> I think the later is better, you can always add a symlink for the
>> firmware name, and you can discern mx8mn/mp firmwares on the same rootfs
>> in case that was ever needed in the future.

Which is what this part of my comment ^ is all about.

  reply	other threads:[~2023-09-01 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  4:44 Adam Ford
2023-08-31  4:44 ` [PATCH V3 2/3] arm64: dts: imx8mp: Add micfil node Adam Ford
2023-08-31 21:53   ` Marek Vasut
2023-09-01 11:06     ` Adam Ford
2023-09-01 15:49       ` Marek Vasut
2023-09-25  1:12   ` Shawn Guo
2023-10-04  1:12   ` Fabio Estevam
2023-10-04 12:15     ` Adam Ford
2023-08-31  4:44 ` [PATCH V3 3/3] clk: imx8mp: Remove non-existent IMX8MP_CLK_AUDIOMIX_PDM_ROOT Adam Ford
2023-08-31 18:25   ` Rob Herring
2023-08-31 21:52 ` [PATCH V3 1/3] arm64: dts: imx8mp: Add easrc node Marek Vasut
2023-09-01 11:02   ` Adam Ford
2023-09-01 15:47     ` Marek Vasut [this message]
2023-09-25  1:07 ` Shawn Guo
2023-09-25  1:12   ` Shawn Guo
2023-10-04  8:39 ` (subset) " Abel Vesa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ec813ef-aa0d-655e-3f78-7c669d72551c@denx.de \
    --to=marex@denx.de \
    --cc=abelvesa@kernel.org \
    --cc=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®