From: "Jaewon Kim" <jaewon02.kim@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>,
"'Wolfram Sang'" <wsa@kernel.org>,
"'Rob Herring'" <robh+dt@kernel.org>
Cc: "'Chanho Park'" <chanho61.park@samsung.com>,
<linux-i2c@vger.kernel.org>, <linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/2] i2c: exynos5: support USI(Universal Serial Interface)
Date: Mon, 8 Nov 2021 20:22:14 +0900 [thread overview]
Message-ID: <000401d7d492$e157a450$a406ecf0$@samsung.com> (raw)
In-Reply-To: <5b05ff2e-953c-d1a3-8347-4d3f9911cc49@canonical.com>
Hello Krzysztof
> On 04/11/2021 09:10, Jaewon Kim wrote:
> >
> >>> + if (ret) {
> >>> + dev_err(dev, "usi-sysreg offset is not specified\n");
> >>> + return ret;
> >>> + }
> >>> +
> >>> + regmap_update_bits(i2c->usi_sysreg, i2c->usi_offset,
> >>> + SYSREG_USI_SW_CONF_MASK, SYSREG_I2C_SW_CONF);
> >>> +
> >>> + exynos_usi_reset(i2c);
> >>
> >> You are clearing the reset flag, but not setting it back on probe
> >> failure. What happens if the probe fails after this clear()? E.g.
> >> because of deferred probe? The next probe try will start on a not-reset controller. Will it work?
> >>
> >
> > The user manual guides USI_RESET to be done after changing the system register.
> > For clarity, we will change not only to clear reset, but to clear after reset.
> >
>
> What I meant, is do you handle probe failure correctly (e.g. probe deferral)? It's fine to leave the
> reset cleared after deferred probe?
>
I understood.
In my opinion, rather than resetting USI_CON_RESET in the probe fail case.
It seems it is more clear to set the reset as shown below.
val = readl(i2c->regs + USI_CON);
val |= USI_CON_RESET;
writel(val, i2c->regs + USI_CON);
udelay(1);
val = readl(i2c->regs + USI_CON);
val &= ~USI_CON_RESET;
writel(val, i2c->regs + USI_CON);
> Best regards,
> Krzysztof
Thanks
Jaewon Kim
prev parent reply other threads:[~2021-11-08 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211101114158epcas2p1d0762d52029b1b09912fd99665dd66f5@epcas2p1.samsung.com>
2021-11-01 11:38 ` [PATCH 1/2] i2c: exynos5: support USI(Universal Serial Interface) Jaewon Kim
[not found] ` <CGME20211101114158epcas2p46b50f8d946d59ffaedd203370b81c6ed@epcas2p4.samsung.com>
2021-11-01 11:38 ` [PATCH 2/2] dt-bindings: i2c: exynos5: add exynos-usi-hsi2c compatible Jaewon Kim
2021-11-03 8:42 ` Krzysztof Kozlowski
2021-11-04 8:06 ` Jaewon Kim
2021-11-03 8:51 ` [PATCH 1/2] i2c: exynos5: support USI(Universal Serial Interface) Krzysztof Kozlowski
2021-11-04 8:10 ` Jaewon Kim
2021-11-04 10:41 ` Krzysztof Kozlowski
2021-11-08 11:22 ` Jaewon Kim [this message]
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='000401d7d492$e157a450$a406ecf0$@samsung.com' \
--to=jaewon02.kim@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).