From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Andreas Färber" <afaerber@suse.de>,
"Wolfram Sang" <wsa@kernel.org>, "Peter Rosin" <peda@axentia.se>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-actions@lists.infradead.org
Subject: Re: [PATCH 1/3] i2c: owl: Clear NACK and BUS error bits
Date: Mon, 12 Oct 2020 12:05:35 +0300 [thread overview]
Message-ID: <20201012090535.GA73734@ubuntu2004> (raw)
In-Reply-To: <20201011140948.GC4971@Mani-XPS-13-9360>
On Sun, Oct 11, 2020 at 07:39:48PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Oct 09, 2020 at 12:44:39AM +0300, Cristian Ciocaltea wrote:
> > When the NACK and BUS error bits are set by the hardware, the driver is
> > responsible for clearing them by writing "1" into the corresponding
> > status registers.
> >
> > Hence perform the necessary operations in owl_i2c_interrupt().
> >
> > Fixes: d211e62af466 ("i2c: Add Actions Semiconductor Owl family S900 I2C driver")
> > Reported-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
> Thanks,
> Mani
Thanks for the review,
Cristi
WARNING: multiple messages have this Message-ID (diff)
From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org,
"Peter Rosin" <peda@axentia.se>, "Wolfram Sang" <wsa@kernel.org>,
linux-i2c@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] i2c: owl: Clear NACK and BUS error bits
Date: Mon, 12 Oct 2020 12:05:35 +0300 [thread overview]
Message-ID: <20201012090535.GA73734@ubuntu2004> (raw)
In-Reply-To: <20201011140948.GC4971@Mani-XPS-13-9360>
On Sun, Oct 11, 2020 at 07:39:48PM +0530, Manivannan Sadhasivam wrote:
> On Fri, Oct 09, 2020 at 12:44:39AM +0300, Cristian Ciocaltea wrote:
> > When the NACK and BUS error bits are set by the hardware, the driver is
> > responsible for clearing them by writing "1" into the corresponding
> > status registers.
> >
> > Hence perform the necessary operations in owl_i2c_interrupt().
> >
> > Fixes: d211e62af466 ("i2c: Add Actions Semiconductor Owl family S900 I2C driver")
> > Reported-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
> Thanks,
> Mani
Thanks for the review,
Cristi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-12 9:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 21:44 [PATCH 0/3] Improve Actions Semi Owl I2C driver Cristian Ciocaltea
2020-10-08 21:44 ` Cristian Ciocaltea
2020-10-08 21:44 ` [PATCH 1/3] i2c: owl: Clear NACK and BUS error bits Cristian Ciocaltea
2020-10-08 21:44 ` Cristian Ciocaltea
2020-10-10 11:16 ` Wolfram Sang
2020-10-10 11:16 ` Wolfram Sang
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-12 9:05 ` Cristian Ciocaltea [this message]
2020-10-12 9:05 ` Cristian Ciocaltea
2020-10-08 21:44 ` [PATCH 2/3] i2c: owl: Add support for atomic transfers Cristian Ciocaltea
2020-10-08 21:44 ` Cristian Ciocaltea
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-11 14:09 ` Manivannan Sadhasivam
2020-10-12 9:07 ` Cristian Ciocaltea
2020-10-12 9:07 ` Cristian Ciocaltea
2020-11-03 20:57 ` Wolfram Sang
2020-11-03 20:57 ` Wolfram Sang
2020-10-08 21:44 ` [PATCH 3/3] i2c: owl: Enable asynchronous probing Cristian Ciocaltea
2020-10-08 21:44 ` Cristian Ciocaltea
2020-10-11 14:06 ` Manivannan Sadhasivam
2020-10-11 14:06 ` Manivannan Sadhasivam
2020-10-12 9:08 ` Cristian Ciocaltea
2020-10-12 9:08 ` Cristian Ciocaltea
2020-11-03 20:57 ` Wolfram Sang
2020-11-03 20:57 ` Wolfram Sang
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=20201012090535.GA73734@ubuntu2004 \
--to=cristian.ciocaltea@gmail.com \
--cc=afaerber@suse.de \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=peda@axentia.se \
--cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.