From: Iuliana Prodan <iuliana.prodan@nxp.com>
To: Shengjiu Wang <shengjiu.wang@nxp.com>,
nicoleotsuka@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
shengjiu.wang@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: fsl_sai: fix getting version from VERID
Date: Tue, 7 Feb 2023 13:21:54 +0200 [thread overview]
Message-ID: <115aca23-a47c-3a92-ae19-b4fa71412ca2@nxp.com> (raw)
In-Reply-To: <1675760664-25193-1-git-send-email-shengjiu.wang@nxp.com>
On 2/7/2023 11:04 AM, Shengjiu Wang wrote:
> The version information is at the bit31 ~ bit16 in the VERID
> register, so need to right shift 16bit to get it, otherwise
> the result of comparison "sai->verid.version >= 0x0301" is
> wrong.
>
> Fixes: 99c1e74f25d4 ("ASoC: fsl_sai: store full version instead of major/minor")
> Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> ---
> sound/soc/fsl/fsl_sai.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
> index c365afd6c4ea..1b197478b3d9 100644
> --- a/sound/soc/fsl/fsl_sai.c
> +++ b/sound/soc/fsl/fsl_sai.c
> @@ -1142,6 +1142,7 @@ static int fsl_sai_check_version(struct device *dev)
>
> sai->verid.version = val &
> (FSL_SAI_VERID_MAJOR_MASK | FSL_SAI_VERID_MINOR_MASK);
> + sai->verid.version >>= FSL_SAI_VERID_MINOR_SHIFT;
> sai->verid.feature = val & FSL_SAI_VERID_FEATURE_MASK;
>
> ret = regmap_read(sai->regmap, FSL_SAI_PARAM, &val);
I would put the version in one line, but probably is easier to read this
way.
Also, please explain, in commit message, what and from where is 0x0301 -
might worth adding a macro for this, in another commit, of course.
Otherwise,
Reviewed-by: Iuliana Prodan <iuliana.prodan@nxp.com>
next prev parent reply other threads:[~2023-02-07 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:04 [PATCH] ASoC: fsl_sai: fix getting version from VERID Shengjiu Wang
2023-02-07 11:16 ` Fabio Estevam
2023-02-07 11:21 ` Iuliana Prodan [this message]
2023-02-07 14:06 ` 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=115aca23-a47c-3a92-ae19-b4fa71412ca2@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=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