linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: alfred steele <alfred.jaquez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: "I2C_RDWR" ioctl returning EINVAL on Freescale mxc
Date: Mon, 17 Aug 2009 08:53:14 +0200	[thread overview]
Message-ID: <20090817065313.GJ31727@pengutronix.de> (raw)
In-Reply-To: <528f13590908141409g4b2556e5m10aec0dc15429457-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Alfred,

On Fri, Aug 14, 2009 at 04:09:21PM -0500, alfred steele wrote:
> In my userspace driver for a temp sensor on a i2c bus, i am using the
> /dev interface.  When i use plain read/write syscalls , they seem to
> work just fine. But when i use a combined read/write using the IOCTL
> "I2C_RDWR", i get a return of invalid argument i.e EINVAL from the
> kernel space i2c dev/bus driver.
> 
> int rest  = ioctl(_fd, I2C_RDWR,  trans );
> 
> So basically res gets a value<1 on execution. I am putting in the
> correct slave address. i have double checked on it. What could be the
> other obvious reasons? Could endian ness be an issue as well although
> the userspace is really invisible and if that had been the case i
> would not have got acks from the slave for a i2c scan on the bus.
> i checked the kernel bus driver code for the reason, but cannot figure
> out just by reading the code at this point  as i have a broken h/w.
> iam using the freescale  mxc i2c bus driver on the kernel side.

Can you elaborate:

- which kernel version is that
- which i.MX derivate are you using?

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2009-08-17  6:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 21:09 "I2C_RDWR" ioctl returning EINVAL on Freescale mxc alfred steele
     [not found] ` <528f13590908141409g4b2556e5m10aec0dc15429457-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17  6:53   ` Robert Schwebel [this message]
     [not found]     ` <20090817065313.GJ31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-17 14:51       ` alfred steele
     [not found]         ` <528f13590908170751u4dcf6d8ftb865103b888225e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17 15:01           ` Robert Schwebel
     [not found]             ` <20090817150159.GT31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-17 21:04               ` alfred steele
     [not found]                 ` <528f13590908171404q2aa4f9aaub98a191c91bd2448-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-17 21:21                   ` Robert Schwebel
     [not found]                     ` <20090817212127.GB31727-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-08-18  3:25                       ` alfred steele
     [not found]                         ` <528f13590908172025i276dc634qd0829cfad8c8c608-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-18  6:13                           ` Robert Schwebel

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=20090817065313.GJ31727@pengutronix.de \
    --to=r.schwebel-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=alfred.jaquez-Re5JQEeQqe8AvxtiuMwx3w@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).