All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mitsyanko <i.mitsyanko@samsung.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: e.voevodin@samsung.com, qemu-devel@nongnu.org,
	kyungmin.park@samsung.com, d.solodkiy@samsung.com,
	m.kozlov@samsung.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH V2 1/3] exynos4210: add Exynos4210 i2c implementation
Date: Wed, 21 Mar 2012 17:07:02 +0400	[thread overview]
Message-ID: <4F69D276.5070905@samsung.com> (raw)
In-Reply-To: <CAFEAcA-q5Jn=chfcofwNo-MXudjd18nAKeZ4e881TORhjMO6NA@mail.gmail.com>

On 03/21/2012 03:55 PM, Peter Maydell wrote:
> On 15 March 2012 07:35, Igor Mitsyanko<i.mitsyanko@samsung.com>  wrote:
>> Create 9 exynos4210 i2c interfaces.
>>
>> Signed-off-by: Igor Mitsyanko<i.mitsyanko@samsung.com>
>
> Mostly this looks OK but I still find the i2c slave stuff
> odd -- should the controller really register itself as
> a slave on its own bus? Doesn't this mean that the
> controller can effectively try to talk to itself? Does
> the hardware let you do that?
>

Controller's master and slave i2c interfaces operate on the same single 
bus, so I think it should. It can't talk to itself because controller's 
two modes of operation are mutually exclusive. As I said, I took this 
approach from pxa i2c implementation, the only difference is that they 
register slave interface on a separate bus, but I think it's not right 
to do that.

> I suspect that what's happening here is that the hardware
> lets you put the i2c controller into slave mode so some
> other device on the bus can be a master. But QEMU's
> i2c bus abstraction doesn't cover that use case at all...
>

Yes, I saw this statement in hw/i2c.h (and probably cpu i2c controller 
will never be used as i2c slave device by anyone), but I think we still 
have to implement devices exactly like they described in documentation.

-- 
Mitsyanko Igor
ASWG, Moscow R&D center, Samsung Electronics
email: i.mitsyanko@samsung.com

  reply	other threads:[~2012-03-21 13:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  7:35 [Qemu-devel] [PATCH V2 0/3] Exynos: i2c, gpio and touchscreen support for NURI board Igor Mitsyanko
2012-03-15  7:35 ` [Qemu-devel] [PATCH V2 1/3] exynos4210: add Exynos4210 i2c implementation Igor Mitsyanko
2012-03-15 10:35   ` Andreas Färber
2012-03-21 11:55   ` Peter Maydell
2012-03-21 13:07     ` Igor Mitsyanko [this message]
2012-03-21 13:09       ` Peter Maydell
2012-03-21 14:18         ` Igor Mitsyanko
2012-03-21 14:24           ` Peter Maydell
2012-04-03 13:54   ` Dmitry Zhurikhin
2012-04-03 14:54     ` Igor Mitsyanko
2012-03-15  7:35 ` [Qemu-devel] [PATCH V2 2/3] exynos4210: add exynos4210 GPIO implementation Igor Mitsyanko
2012-03-15 11:06   ` Andreas Färber
2012-03-20 13:27   ` Peter Maydell
2012-03-21 13:01     ` Igor Mitsyanko
2012-03-15  7:35 ` [Qemu-devel] [PATCH V2 3/3] hw: add Atmel maxtouch touchscreen implementation Igor Mitsyanko
2012-03-15  9:48   ` Andreas Färber
2012-03-15 10:25     ` Dmitry Solodkiy
2012-03-15 10:41     ` Igor Mitsyanko

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=4F69D276.5070905@samsung.com \
    --to=i.mitsyanko@samsung.com \
    --cc=afaerber@suse.de \
    --cc=d.solodkiy@samsung.com \
    --cc=e.voevodin@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=m.kozlov@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.