lkml.org 
[lkml]   [2016]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [lkp] [gpio] 1b06d64f73: kmsg.dio-#e#-dio-#e:Unable_to_lock#-dio-#e_port_addresses(#-#)
From
Date
On 01/31/2016 08:14 PM, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
> commit 1b06d64f73746c30ddba43bb57c30ba9a126f53b ("gpio: Add GPIO support for the ACCES 104-DIO-48E")
>
> With your commit, there are the following new messages in kernel log.
>
> [ 6.176052] 104-dio-48e 104-dio-48e: Unable to lock 104-dio-48e port addresses (0x0-0x10)
> [ 6.176052] 104-dio-48e 104-dio-48e: Unable to lock 104-dio-48e port addresses (0x0-0x10)
> [ 6.177538] 104-dio-48e: probe of 104-dio-48e failed with error -16
> [ 6.177538] 104-dio-48e: probe of 104-dio-48e failed with error -16
> [ 6.178846] 104-idi-48 104-idi-48: Unable to lock 104-idi-48 port addresses (0x0-0x8)
> [ 6.178846] 104-idi-48 104-idi-48: Unable to lock 104-idi-48 port addresses (0x0-0x8)
> [ 6.180359] 104-idi-48: probe of 104-idi-48 failed with error -16
> [ 6.180359] 104-idi-48: probe of 104-idi-48 failed with error -16
>
> Thanks,
> Ying Huang

This behavior is expected for the 104-dio-48e module and 104-idi-48
module: base port address for the hardware must be manually set by the
user since the hardware lacks discovery functionality.

William Breathitt Gray

\
 
 \ /
  Last update: 2016-02-01 02:41    [W:0.272 / U:0.308 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site