All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Bachmeier <michael.bachmeier.linux@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, kernel@pengutronix.de,
	Shawn Guo <shawn.guo@linaro.org>
Subject: Re: i2c slave support für i.mx6
Date: Mon, 23 Nov 2015 10:11:24 +0100	[thread overview]
Message-ID: <CAH-Fpeo6R1haEb0qdw5merP5tpAhaEL7FKJ3HV6WFLfiB_B0Cg@mail.gmail.com> (raw)
In-Reply-To: <20151118111142.GC11028@katana>

Hi,

Is the recognition of IAAS a hardware interrupt (according to manual,
yes)? I set IEN (I2C enable) and IIEN (Interrupt Enable).
I set the slave address to 0x1c (chosen at random). The IMX bus driver
is unchanged. With my external Master I ask for the address on the
bus. But the IAAS bit is never set.
In this test, I want to see if the hardware interrupt work.
Should i modified the bus driver (IRQ handler???) or is this a real
hardware interrupt?

Where is my misconception?

Best regards

2015-11-18 12:11 GMT+01:00 Wolfram Sang <wsa@the-dreams.de>:
> Hi,
>
>> thanks to your comments in the rcar driver, I understand the function
>> of each register. But I'd like a manual of this board. Where is
>> accurately entered into the individual registers.
>
> As far as I know, there is no public user manual for RCar SoCs. I can
> ask, though.
>
>> Had someone for me a manual by the individual registers are explained.
>> So that I can understand the rcar driver better.
>
> However, if you have a specific question, you could ask and I could try
> improving the driver's documentation :)
>
> Regards,
>
>    Wolfram
>

  reply	other threads:[~2015-11-23  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  8:06 i2c slave support für i.mx6 Michael Bachmeier
2015-11-10  8:59 ` Wolfram Sang
2015-11-16  6:47   ` Michael Bachmeier
2015-11-18 11:11     ` Wolfram Sang
2015-11-23  9:11       ` Michael Bachmeier [this message]
2015-11-24  8:08         ` Wolfram Sang

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=CAH-Fpeo6R1haEb0qdw5merP5tpAhaEL7FKJ3HV6WFLfiB_B0Cg@mail.gmail.com \
    --to=michael.bachmeier.linux@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=wsa@the-dreams.de \
    /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.