linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Felipe Balbi <balbi@ti.com>
Cc: Alexander Kochetkov <al.kochet@gmail.com>,
	linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 2/2] i2c: omap: fix "Too much work in one IRQ" irq handling
Date: Mon, 17 Nov 2014 15:41:53 +0100	[thread overview]
Message-ID: <20141117144152.GA12644@katana> (raw)
In-Reply-To: <20141116154558.GA7422@saruman>

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]


> > submit write request to General Call Address. In that case ISR could
> > not correctly handle RDR (or XRDY, ARDY, or that ever). Thats becase
> > i2c-omap driver doesn't correctly handle i2c-controller's slave mode.
> 
> right, Linux doesn't support being the slave. That's also a missing
> feature, not a bug.

This is going to change. I sent out RFC patches for slave support [1]
and will send V1 this week. This won't affect your driver, though,
unless you implement the backend into it.

Just to keep your heads up.

[1] http://thread.gmane.org/gmane.linux.kernel/1783295

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-11-17 14:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15  1:20 [PATCH 1/2] i2c: omap: fix NACK and Arbitration Lost irq handling Alexander Kochetkov
     [not found] ` <1416014452-6712-1-git-send-email-al.kochet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-15  1:20   ` [PATCH 2/2] i2c: omap: fix "Too much work in one IRQ" " Alexander Kochetkov
     [not found]     ` <1416014452-6712-2-git-send-email-al.kochet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-15  1:48       ` Felipe Balbi
2014-11-15  2:37         ` Alexander Kochetkov
2014-11-15  3:47           ` Felipe Balbi
2014-11-15  3:53             ` Felipe Balbi
2014-11-15  5:42               ` Alexander Kochetkov
2014-11-16 15:45                 ` Felipe Balbi
2014-11-17 14:41                   ` Wolfram Sang [this message]
2014-11-18 16:00                     ` Felipe Balbi
2014-11-18 16:12                       ` Wolfram Sang
2014-11-20 16:38                         ` Alexander Kochetkov
     [not found]                           ` <2DED62C3-7C54-49E0-A39B-F68D5DAC66B1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-20 16:43                             ` Wolfram Sang
2014-11-18 16:31                       ` Alexander Kochetkov
     [not found]                         ` <5D39428D-F359-4F04-8ACC-D607011B88B9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-18 16:38                           ` Felipe Balbi
2014-11-15  1:43   ` [PATCH 1/2] i2c: omap: fix NACK and Arbitration Lost " Felipe Balbi
     [not found]     ` <2159E044-9130-410D-905B-B941408DCDCD@gmail.com>
     [not found]       ` <2159E044-9130-410D-905B-B941408DCDCD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-15  2:48         ` Alexander Kochetkov

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=20141117144152.GA12644@katana \
    --to=wsa@the-dreams.de \
    --cc=al.kochet@gmail.com \
    --cc=balbi@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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).