From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: lkp@lists.01.org
Subject: Re: [gpio] 1b06d64f73: kmsg.dio-#e#-dio-#e:Unable_to_lock#-dio-#e_port_addresses(#-#)
Date: Sun, 31 Jan 2016 20:20:33 -0500 [thread overview]
Message-ID: <56AEB2E1.5070307@gmail.com> (raw)
In-Reply-To: <877fipkz99.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
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
WARNING: multiple messages have this Message-ID (diff)
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [lkp] [gpio] 1b06d64f73: kmsg.dio-#e#-dio-#e:Unable_to_lock#-dio-#e_port_addresses(#-#)
Date: Sun, 31 Jan 2016 20:20:33 -0500 [thread overview]
Message-ID: <56AEB2E1.5070307@gmail.com> (raw)
In-Reply-To: <877fipkz99.fsf@yhuang-dev.intel.com>
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
next prev parent reply other threads:[~2016-02-01 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 1:14 [gpio] 1b06d64f73: kmsg.dio-#e#-dio-#e:Unable_to_lock#-dio-#e_port_addresses(#-#) kernel test robot
2016-02-01 1:14 ` [lkp] " kernel test robot
2016-02-01 1:20 ` William Breathitt Gray [this message]
2016-02-01 1:20 ` William Breathitt Gray
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=56AEB2E1.5070307@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=lkp@lists.01.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.