From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: "Mårten Lindahl" <marten.lindahl@axis.com>,
kernel@axis.com, "Mårten Lindahl" <martenli@axis.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: exynos5: Preserve high speed master code
Date: Fri, 26 Feb 2021 11:40:00 +0100 [thread overview]
Message-ID: <CAJKOXPcx5a7m0ChqA8BimK=JhnzSgm0cx07RhSu+P8D-2YsfWw@mail.gmail.com> (raw)
In-Reply-To: <20210226103407.GF1014@ninjato>
On Fri, 26 Feb 2021 at 11:34, Wolfram Sang <wsa@kernel.org> wrote:
>
> On Tue, Feb 16, 2021 at 11:25:38PM +0100, Mårten Lindahl wrote:
> > From: Mårten Lindahl <martenli@axis.com>
> >
> > When the driver starts to send a message with the MASTER_ID field
> > set (high speed), the whole I2C_ADDR register is overwritten including
> > MASTER_ID as the SLV_ADDR_MAS field is set.
> >
> > This patch preserves already written fields in I2C_ADDR when writing
> > SLV_ADDR_MAS.
> >
> > Signed-off-by: Mårten Lindahl <martenli@axis.com>
>
> Looks good. Is there a Fixes-tag we could apply?
The first commit, 2013 :)
Fixes: 8a73cd4cfa15 ("i2c: exynos5: add High Speed I2C controller driver")
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-02-26 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 22:25 [PATCH v2] i2c: exynos5: Preserve high speed master code Mårten Lindahl
2021-02-17 8:35 ` Krzysztof Kozlowski
2021-02-26 10:34 ` Wolfram Sang
2021-02-26 10:40 ` Krzysztof Kozlowski [this message]
2021-02-26 10:48 ` 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='CAJKOXPcx5a7m0ChqA8BimK=JhnzSgm0cx07RhSu+P8D-2YsfWw@mail.gmail.com' \
--to=krzk@kernel.org \
--cc=kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marten.lindahl@axis.com \
--cc=martenli@axis.com \
--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 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).