linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: w1-gpio oops
Date: Tue, 09 Nov 2010 16:51:34 +0100	[thread overview]
Message-ID: <87lj524hrt.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <8D0E58DD-1923-4321-A0B3-9FBD2DDA3529@gmail.com> (Alan Pearson's message of "Tue, 9 Nov 2010 15:40:19 +0000")

Alan Pearson <alandpearson@gmail.com> writes:

Hi,

>>> ----- Original Message ----- From: "Alan Pearson" <alandpearson@gmail.com>
>>> To: <linux-arm-kernel@lists.infradead.org>
>>> Sent: Tuesday, November 09, 2010 7:29 PM
>>> Subject: w1-gpio oops
>>> 
>>> 
>>>> Hi Guys,
>>>> 
>>>> First post to list, so be kind :)
>>>> 
>>>> I'm trying to get w1 (one wire) working over GPIO and despite my best efforts this results in a nasty oops.
>>>> Firstly, I'd like to say I'm no kernel hacker and my knowledge of Ooops and kernel debugging is limited, but I'm willing to learn:)
>>> 
>>> Common cause for these errors could be nonexistent or incorrect platform data. Might be worth checking if w1_gpio_platform_data
>>> is proper in your board file. You could look for examples in other board files like arch/arm/mach-pxa/raumfeld.c
>>> 
>> 
>> <CHOP>
>> 
>> Ok, I had understood the platform data was being set in the w1_gpio_custom module by the loadable options.
>> Is this not the case, or does it also need defined in the board file, which I presume is guruplug_setup.c ?
>> It's currently not defined there. But as I said I expected the other module to do this, am I wrong ?
>> 
>> 
>> Looking at the function w1_gpio_probe, it doesnot seem to be using module params. So u might need to define those
>> in your board file.
>> 
>
> OK, I've modified my board file like so (guruplug-setup.c) :
>
>
> static struct w1_gpio_platform_data guru_gpio_platform_data = {
>         .pin                    = MPP38_GPIO,

It's 38 not MPP38_GPIO. MPP38_GPIO is for the guruplug_mpp_config[]
stuff (looks at how the leds are configured for instance)


Arnaud

  reply	other threads:[~2010-11-09 15:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 13:59 w1-gpio oops Alan Pearson
2010-11-09 14:29 ` Hemanth V
2010-11-09 14:44   ` Alan Pearson
2010-11-09 14:53     ` Hemanth V
2010-11-09 14:56       ` Alan Pearson
2010-11-09 15:40       ` Alan Pearson
2010-11-09 15:51         ` Arnaud Patard (Rtp) [this message]
2010-11-09 16:52           ` Alan Pearson

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=87lj524hrt.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=linux-arm-kernel@lists.infradead.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).