From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: cm-hiep@jinso.co.jp
Cc: "Magnus Damm" <damm@opensource.se>,
"Simon Horman" <simon@horms.net>,
linux-gpio@vger.kernel.org, "Simon Horman" <horms@verge.net.au>,
"Kuninori Morimoto" <kuninori.morimoto.gx@gmail.com>,
S開12/森本さん <kuninori.morimoto.gx@renesas.com>,
SH-Linux <linux-sh@vger.kernel.org>
Subject: Re: [Bug] GPIO-Rcar: Driver does not work after Unbind-rebind.
Date: Tue, 05 Aug 2014 03:05:04 +0200 [thread overview]
Message-ID: <11539044.7ozDkqgRA7@avalon> (raw)
In-Reply-To: <53DB3E53.2000508@jinso.co.jp>
Hello,
On Friday 01 August 2014 16:14:27 カオ ミン ヒェップ wrote:
> Hello,
>
> I tested gpio-rcar driver at Linux-upstream-v3.16-rc5 on Lager.
> When I tried to unbind and then rebind the device, error messages occur.
> Then gpio-rcar did not work and interrupt number did not count up any more.
>
> The error messages is showed as below:
> "irq 0, desc: ee005040, depth: 1, cou0
> ->handle_irq(): c005eea0, handle_bad_irq+0x0/0x21c
> ->irq_data.chip(): c05de7f8, 0xc05de7f8
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set
> irq 0, desc: ee005040, depth: 1, count: 0, unhandled: 0
> ->handle_irq(): c005eea0, handle_bad_irq+0x0/0x21c
> ->irq_data.chip(): c05de7f8, 0xc05de7f8
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set"
>
> Please see it and fix this bug.
Could you please detail the procedure to follow to reproduce the problem ?
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-05 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 7:14 [Bug] GPIO-Rcar: Driver does not work after Unbind-rebind カオ ミン ヒェップ
2014-08-05 1:05 ` Laurent Pinchart [this message]
2014-08-05 2:37 ` カオ ミン ヒェップ
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=11539044.7ozDkqgRA7@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=cm-hiep@jinso.co.jp \
--cc=damm@opensource.se \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=simon@horms.net \
/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).