public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil <phil-FnsA7b+Nu9XbIbC87yuRow@public.gmane.org>
To: Stefan Wahren <info-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
Cc: linux-rpi-kernel
	<linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c-bcm2835: Unable to read from i2c0
Date: Fri, 29 Jan 2016 18:47:02 +0000	[thread overview]
Message-ID: <f9322494-c373-47ff-8680-f51751e37df3@email.android.com> (raw)
In-Reply-To: <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>

> > 2) What is the state of the GPIOs? 
>
> What do you mean? configuration of both I2C0 pins? 
>
> Do you want a register dump? 

There are a number of utilities that will display the configuration of all pins - raspi-gpio is the one I use. My intention was to confirm that the I2C0 function was not multiply mapped, but you can do that yourself, and from what you say it probably isn't.

You are likely to get more answers on the Raspberry Pi forums.

      parent reply	other threads:[~2016-01-29 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 21:43 i2c-bcm2835: Unable to read from i2c0 Stefan Wahren
     [not found] ` <56AA8B75.9060801-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
2016-01-28 22:49   ` Phil
     [not found]     ` <7de3fd0b-7973-476c-a009-e9a1fb032a80-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2016-01-29 18:16       ` Stefan Wahren
     [not found]         ` <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
2016-01-29 18:47           ` Phil [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=f9322494-c373-47ff-8680-f51751e37df3@email.android.com \
    --to=phil-fnsa7b+nu9xbibc87yurow@public.gmane.org \
    --cc=info-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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