From: Wolfram Sang <wsa@the-dreams.de>
To: Andrey Danin <danindrey@mail.ru>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
ac100@lists.launchpad.net, Laxman Dewangan <ldewangan@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
Marc Dietrich <marvin24@gmx.de>
Subject: Re: [PATCH 1/3] i2c: tegra: implement slave mode
Date: Thu, 29 Jan 2015 12:41:55 +0100 [thread overview]
Message-ID: <20150129114155.GA9080@katana> (raw)
In-Reply-To: <1422516022-27161-2-git-send-email-danindrey@mail.ru>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
Hi,
> Initialization code is based on NVEC driver.
>
> There is a HW bug in AP20 that was also mentioned in kernel sources
> for Toshiba AC100.
>
> Signed-off-by: Andrey Danin <danindrey@mail.ru>
Cool, thanks for the converison. While I usually like to only get the
patches which I need to handle, please CC me to all patches next time. I
am interested what changes were needed for the user of the slave
framework, too.
> +static bool tegra_i2c_slave_isr(int irq, struct tegra_i2c_dev *i2c_dev)
> +{
> + unsigned long status;
> + u8 value;
> +
> + if (!i2c_dev->slave || !i2c_dev->slave->slave_cb)
> + return false;
Can this happen?
> + /* i2c master sends data to us */
> + if (is_write(status)) {
> + i2c_slave_event(i2c_dev->slave, I2C_SLAVE_REQ_WRITE_START,
> + NULL);
Can this HW create an interrupt once the address detection + RW bit are
received? Or only if a complete write has been received?
> +static int tegra_reg_slave(struct i2c_client *slave)
> +{
> + struct tegra_i2c_dev *i2c_dev = i2c_get_adapdata(slave->adapter);
> +
> + if (i2c_dev->slave)
> + return -EBUSY;
> +
> + i2c_dev->slave = slave;
> +
> + tegra_i2c_clock_enable(i2c_dev);
> +
> + reset_control_assert(i2c_dev->rst);
> + udelay(2);
> + reset_control_deassert(i2c_dev->rst);
Why do you need a reset when a slave gets registered?
> +
> + i2c_writel(i2c_dev, I2C_SL_CNFG_NEWSL, I2C_SL_CNFG);
> + i2c_writel(i2c_dev, 0x1E, I2C_SL_DELAY_COUNT);
What does this magic number mean?
> +
> + i2c_writel(i2c_dev, slave->addr, I2C_SL_ADDR1);
> + i2c_writel(i2c_dev, 0, I2C_SL_ADDR2);
Handling 10 bit addresses?
> +
> + return 0;
> +}
> +
> static const struct tegra_i2c_hw_feature tegra30_i2c_hw = {
> @@ -679,6 +808,7 @@ static const struct tegra_i2c_hw_feature tegra30_i2c_hw = {
> .has_single_clk_source = false,
> .clk_divisor_hs_mode = 3,
> .clk_divisor_std_fast_mode = 0,
> + .slave_read_start_delay = 0,
No need to init to 0 IMO.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-29 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 7:20 [PATCH 0/3] arm: tegra: implement NVEC driver using tegra i2c Andrey Danin
2015-01-29 7:20 ` [PATCH 1/3] i2c: tegra: implement slave mode Andrey Danin
2015-01-29 9:40 ` Marc Dietrich
2015-01-29 11:41 ` Wolfram Sang [this message]
2015-03-31 6:25 ` Andrey Danin
[not found] ` <1422516022-27161-4-git-send-email-danindrey@mail.ru>
[not found] ` <54CFEA2F.8040701@wwwdotorg.org>
[not found] ` <551A415B.4040506@mail.ru>
[not found] ` <551AAA9B.6070607@wwwdotorg.org>
[not found] ` <551AC153.7060103@mail.ru>
[not found] ` <551AC153.7060103-JGs/UdohzUI@public.gmane.org>
2015-03-31 16:04 ` [PATCH 3/3] dt: paz00: define nvec as child of i2c bus Andrey Danin
[not found] ` <551C2AC0.9030304@wwwdotorg.org>
[not found] ` <551C2AC0.9030304-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-04-02 9:37 ` Marc Dietrich
2015-04-02 14:50 ` Stephen Warren
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=20150129114155.GA9080@katana \
--to=wsa@the-dreams.de \
--cc=ac100@lists.launchpad.net \
--cc=danindrey@mail.ru \
--cc=gnurou@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).