mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Iuliana Prodan <iuliana.prodan@nxp.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>,
	shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
	nicoleotsuka@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
	perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org,
	linuxppc-dev@lists.ozlabs.org, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ASoC: fsl_micfil: Check the difference for i.MX8 and i.MX9
Date: Mon, 29 Jul 2024 11:02:04 +0300	[thread overview]
Message-ID: <d3a4654c-7d20-4a21-8fff-fb5dc0076547@nxp.com> (raw)
In-Reply-To: <1721897694-6088-1-git-send-email-shengjiu.wang@nxp.com>

On 7/25/2024 11:54 AM, Shengjiu Wang wrote:
> There are some register difference for i.MX8 and i.MX9
> REG_MICFIL_FIFO_CTRL definition is updated.
> REG_MICFIL_FSYNC_CTRL, REG_MICFIL_VERID, REG_MICFIL_PARAM are added from
> i.MX9
>
> Shengjiu Wang (2):
>    ASoC: fsl_micfil: Expand the range of FIFO watermark mask
>    ASoC: fsl_micfil: Differentiate register access permission for
>      platforms
>
>   sound/soc/fsl/fsl_micfil.c | 20 +++++++++++++++-----
>   sound/soc/fsl/fsl_micfil.h |  2 +-
>   2 files changed, 16 insertions(+), 6 deletions(-)

For the series: Reviewed-by: Iuliana Prodan <iuliana.prodan@nxp.com>

Thanks, Iulia


  parent reply	other threads:[~2024-07-29  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  8:54 Shengjiu Wang
2024-07-25  8:54 ` [PATCH 1/2] ASoC: fsl_micfil: Expand the range of FIFO watermark mask Shengjiu Wang
2024-07-25  8:54 ` [PATCH 2/2] ASoC: fsl_micfil: Differentiate register access permission for platforms Shengjiu Wang
2024-07-29  8:02 ` Iuliana Prodan [this message]
2024-07-31 13:53 ` [PATCH 0/2] ASoC: fsl_micfil: Check the difference for i.MX8 and i.MX9 Mark Brown

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=d3a4654c-7d20-4a21-8fff-fb5dc0076547@nxp.com \
    --to=iuliana.prodan@nxp.com \
    --cc=Xiubo.Lee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=shengjiu.wang@gmail.com \
    --cc=shengjiu.wang@nxp.com \
    --cc=tiwai@suse.com \
    /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®