From: Andreas Schwab <schwab@linux-m68k.org>
To: Sagar Shrikant Kadam <sagar.kadam@sifive.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-i2c@vger.kernel.org, peter@korsgaard.com, andrew@lunn.ch,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v2 1/1] i2c: ocores: fix polling mode workaround on FU540-C000 SoC
Date: Fri, 09 Oct 2020 20:24:34 +0200 [thread overview]
Message-ID: <87pn5rp89p.fsf@igel.home> (raw)
In-Reply-To: <1602257980-375157-2-git-send-email-sagar.kadam@sifive.com> (Sagar Shrikant Kadam's message of "Fri, 9 Oct 2020 08:39:40 -0700")
On Okt 09 2020, Sagar Shrikant Kadam wrote:
> diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
> index f5fc75b..9b3d1ab 100644
> --- a/drivers/i2c/busses/i2c-ocores.c
> +++ b/drivers/i2c/busses/i2c-ocores.c
> @@ -686,17 +686,21 @@ static int ocores_i2c_probe(struct platform_device *pdev)
>
> init_waitqueue_head(&i2c->wait);
>
> + /*
> + * Set OCORES_FLAG_BROKEN_IRQ to enable workaround for
> + * FU540-C000 SoC in polling mode.
> + * Since the SoC does have interrupt it's dt has the interrupt
Typo: its
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-10-09 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 15:39 [PATCH v2 0/1] fix i2c polling mode workaround for FU540-C000 SoC Sagar Shrikant Kadam
2020-10-09 15:39 ` [PATCH v2 1/1] i2c: ocores: fix polling mode workaround on " Sagar Shrikant Kadam
2020-10-09 18:24 ` Andreas Schwab [this message]
2020-10-12 15:49 ` Sagar Kadam
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=87pn5rp89p.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peter@korsgaard.com \
--cc=sagar.kadam@sifive.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;
as well as URLs for NNTP newsgroup(s).