From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Myunguk Kim <mwkim@gaonchips.com>, alsa-devel@alsa-project.org
Cc: broonie@kernel.org, fido_max@inbox.ru,
kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, perex@perex.cz, tiwai@suse.com,
u.kleine-koenig@pengutronix.de, xingyu.wu@starfivetech.com
Subject: Re: [PATCH] [v2] ASoC: dwc: fix typo in comment
Date: Wed, 13 Sep 2023 14:27:09 +0700 [thread overview]
Message-ID: <ZQFkTYqZ-QWxCjFu@debian.me> (raw)
In-Reply-To: <20230913024103.1454354-1-mwkim@gaonchips.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Wed, Sep 13, 2023 at 11:41:04AM +0900, Myunguk Kim wrote:
> ISR_RXFO means "Status of Data Overrun interrupt for the RX channel"
> according to the datasheet.
>
> So, the comment should be RX, not TX
Thanks for better description!
The patch title though, I'd like to write it as "ASoC: dwc: correct ISR_RXFO
check comment".
>
> Signed-off-by: Myunguk Kim <mwkim@gaonchips.com>
> ---
> sound/soc/dwc/dwc-i2s.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/dwc/dwc-i2s.c b/sound/soc/dwc/dwc-i2s.c
> index 22c004179214..c71c17ef961d 100644
> --- a/sound/soc/dwc/dwc-i2s.c
> +++ b/sound/soc/dwc/dwc-i2s.c
> @@ -138,7 +138,7 @@ static irqreturn_t i2s_irq_handler(int irq, void *dev_id)
> irq_valid = true;
> }
>
> - /* Error Handling: TX */
> + /* Error Handling: RX */
> if (isr[i] & ISR_RXFO)
> { dev_err_ratelimited(dev->dev, "RX overrun (ch_id=%d)\n", i);
> irq_valid = true;
In any case,
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-13 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 2:41 [PATCH] [v2] ASoC: dwc: fix typo in comment Myunguk Kim
2023-09-13 7:27 ` Bagas Sanjaya [this message]
2023-09-13 17:52 ` Mark Brown
2023-09-14 0:56 ` Myunguk Kim
2023-09-14 6:32 ` Uwe Kleine-König
2023-09-14 11:42 ` 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=ZQFkTYqZ-QWxCjFu@debian.me \
--to=bagasdotme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fido_max@inbox.ru \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwkim@gaonchips.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=xingyu.wu@starfivetech.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