All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Clapson <jonathan.clapson@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: iio_trigger_alloc fails on Raspberry pi
Date: Tue, 30 Jul 2013 23:32:33 +0100	[thread overview]
Message-ID: <51F83F01.4070509@kernel.org> (raw)
In-Reply-To: <CAFBKNSRAqprfNZzBVvPR3tqMPip4G9mz3nNDFqUkRB71MqR48w@mail.gmail.com>

On 07/30/13 04:39, Jonathan Clapson wrote:
> Hey
> 
> I'm trying to write a driver to interact with the mpu6000 imu sensor
> on the raspberry pi.
> I've modified the mpu6050 i2c driver in the linux kernel to use the
> mpu6000's spi interface. Calls of iio_trigger_alloc fail. I've added
> some debugging info to industrialio-trigger.c and from this have
> narrowed it down to the irq_alloc_descs function failing to allocate
> any irq's.
> 
> cat /proc/interrupts returns:
>            CPU0
>   3:      21114   ARMCTRL  BCM2708 Timer Tick
>  32:     986019   ARMCTRL  dwc_otg, dwc_otg_pcd, dwc_otg_hcd:usb1
>  65:          7   ARMCTRL  ARM Mailbox IRQ
>  66:          1   ARMCTRL  VCHIQ doorbell
>  75:          1   ARMCTRL
>  77:       6801   ARMCTRL  bcm2708_sdhci (dma)
>  80:         30   ARMCTRL  bcm2708_spi.0
>  83:         20   ARMCTRL  uart-pl011
>  84:      11002   ARMCTRL  mmc0
> FIQ:              usb_fiq
> Err:          0
> 
> The call to irq_alloc_descs seems to be trying to allocate *any* two
> consecutive irq's (two being the value of
> CONFIG_IIO_CONSUMERS_PER_TRIGGER), the above i believe shows that this
> should be possible?
> 
> Any idea's why irq_alloc_descs is failing?
It has been a while since I last came across anything similar but this is probably
due to the underlying raspberry pi kernel restricting your available interrupts.
In at least some boards it is still necessary to explicitly allocate a few more
in the board config file or equivalent.



> 
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2013-07-30 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  3:39 iio_trigger_alloc fails on Raspberry pi Jonathan Clapson
2013-07-30 22:32 ` Jonathan Cameron [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=51F83F01.4070509@kernel.org \
    --to=jic23@kernel.org \
    --cc=jonathan.clapson@gmail.com \
    --cc=linux-iio@vger.kernel.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.