linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Porotchkin <kostap-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Fix I2C combined access on Marvell mv64xxxx
Date: Mon, 2 May 2011 17:53:22 +0300	[thread overview]
Message-ID: <BANLkTinV9g9KypLm5d=qDB4a943GoMYU6A@mail.gmail.com> (raw)
In-Reply-To: <1301582411-2437-1-git-send-email-kostap-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>

Hello, Ben,

Are you going to integrate Marvel's i2c patches dated March 31 to the
kernel tree?

Thank you for your help
Konstantin

On Thu, Mar 31, 2011 at 5:40 PM, Konstantin Porotchkin
<kostap-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org> wrote:
> Eliminate erroneus data send in combined access mode when INT
> is cleared in i2c controller. Instead disable INT delivery to CPU
> and re-enable it on the next START.
>
> Signed-off-by: Konstantin Porotchkin <kostap-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
> ---
>  drivers/i2c/busses/i2c-mv64xxx.c |   19 +++++++++++++++----
>  1 files changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-mv64xxx.c b/drivers/i2c/busses/i2c-mv64xxx.c
> index a9941c6..d013e25 100644
> --- a/drivers/i2c/busses/i2c-mv64xxx.c
> +++ b/drivers/i2c/busses/i2c-mv64xxx.c
> @@ -15,6 +15,7 @@
>  #include <linux/spinlock.h>
>  #include <linux/i2c.h>
>  #include <linux/interrupt.h>
> +#include <linux/delay.h>
>  #include <linux/mv643xx_i2c.h>
>  #include <linux/platform_device.h>
>  #include <linux/io.h>
> @@ -98,6 +99,7 @@ struct mv64xxx_i2c_data {
>        int                     rc;
>        u32                     freq_m;
>        u32                     freq_n;
> +       int                     irq_disabled;
>        wait_queue_head_t       waitq;
>        spinlock_t              lock;
>        struct i2c_msg          *msg;
> @@ -239,10 +241,11 @@ mv64xxx_i2c_do_action(struct mv64xxx_i2c_data *drv_data)
>  {
>        switch(drv_data->action) {
>        case MV64XXX_I2C_ACTION_SEND_RESTART:
> -               drv_data->cntl_bits |= MV64XXX_I2C_REG_CONTROL_START;
> -               drv_data->cntl_bits &= ~MV64XXX_I2C_REG_CONTROL_INTEN;
> -               writel(drv_data->cntl_bits,
> -                       drv_data->reg_base + MV64XXX_I2C_REG_CONTROL);
> +               /* can't mask interrupts by clearing the INTEN as this
> +                * triggers the controller to send the data.
> +                */
> +               drv_data->irq_disabled = 1;
> +               disable_irq_nosync(drv_data->irq);
>                drv_data->block = 0;
>                wake_up_interruptible(&drv_data->waitq);
>                break;
> @@ -255,6 +258,11 @@ mv64xxx_i2c_do_action(struct mv64xxx_i2c_data *drv_data)
>        case MV64XXX_I2C_ACTION_SEND_START:
>                writel(drv_data->cntl_bits | MV64XXX_I2C_REG_CONTROL_START,
>                        drv_data->reg_base + MV64XXX_I2C_REG_CONTROL);
> +               if (drv_data->irq_disabled) {
> +                       udelay(3);
> +                       drv_data->irq_disabled = 0;
> +                       enable_irq(drv_data->irq);
> +               }
>                break;
>
>        case MV64XXX_I2C_ACTION_SEND_ADDR_1:
> @@ -327,6 +335,8 @@ mv64xxx_i2c_intr(int irq, void *dev_id)
>                mv64xxx_i2c_fsm(drv_data, status);
>                mv64xxx_i2c_do_action(drv_data);
>                rc = IRQ_HANDLED;
> +               if (drv_data->state == MV64XXX_I2C_STATE_WAITING_FOR_RESTART)
> +                       break;
>        }
>        spin_unlock_irqrestore(&drv_data->lock, flags);
>
> @@ -553,6 +563,7 @@ mv64xxx_i2c_probe(struct platform_device *pd)
>                rc = -ENXIO;
>                goto exit_unmap_regs;
>        }
> +       drv_data->irq_disabled = 0;
>        drv_data->adapter.dev.parent = &pd->dev;
>        drv_data->adapter.algo = &mv64xxx_i2c_algo;
>        drv_data->adapter.owner = THIS_MODULE;
> --
> 1.7.4.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      parent reply	other threads:[~2011-05-02 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 14:40 [PATCH] Fix I2C combined access on Marvell mv64xxxx Konstantin Porotchkin
     [not found] ` <1301582411-2437-1-git-send-email-kostap-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2011-03-31 14:40   ` [PATCH] Add-delay-after-setting-the-STOP-bit-i2c-mv64xxx Konstantin Porotchkin
2011-03-31 14:40   ` [PATCH] Dove - Support init val. for i2c delay after STOP Konstantin Porotchkin
2011-03-31 14:40   ` [PATCH] Support power management in i2c mv64xx driver Konstantin Porotchkin
2011-03-31 14:40   ` [PATCH] Support i2c expander on mv64xxx adapter Konstantin Porotchkin
2011-05-02 14:53   ` Konstantin Porotchkin [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='BANLkTinV9g9KypLm5d=qDB4a943GoMYU6A@mail.gmail.com' \
    --to=kostap-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).