From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <tony@atomide.com>
Cc: <bcousson@baylibre.com>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<j-keerthy@ti.com>
Subject: [PATCH 0/4] ARM: dts: am437x boards: Correct tps65218 irq type
Date: Fri, 20 Apr 2018 14:38:18 +0300 [thread overview]
Message-ID: <20180420113822.17577-1-peter.ujfalusi@ti.com> (raw)
Hi,
In linux-next I started to see: https://pastebin.com/wrDdptzh
[ 2.813985] ------------[ cut here ]------------
[ 2.818746] WARNING: CPU: 0 PID: 19 at /home/ujfalusi/work/kernel/github.omap-audio.linux-audio/drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate+0xd4/0xec
[ 2.833311] Modules linked in:
[ 2.836417] CPU: 0 PID: 19 Comm: kworker/0:2 Not tainted 4.17.0-rc1-next-20180420-00057-gffd03ee19b9b #182
[ 2.846113] Hardware name: Generic AM43 (Flattened Device Tree)
[ 2.852073] Workqueue: events deferred_probe_work_func
...
Becasue most of the am437x boards had IRQ_TYPE_NONE for tps65218.
According to the datasheet [1] the interrult line is low active, so fix up the board
DTS files.
Interestingly the am437x-sk-evm had IRQ_TYPE_LEVEL_HIGH, which is not matching
with the datasheet.
[1] http://www.ti.com/lit/ds/symlink/tps65218.pdf, page 8.
Regards,
Peter
---
Peter Ujfalusi (4):
ARM: dts: am437x-gp-evm: Correct tps65218 irq type
ARM: dts: am437x-cm-t43: Correct tps65218 irq type
ARM: dts: am437x-epos-evm: Correct tps65218 irq type
ARM: dts: am437x-sk-evm: Correct tps65218 irq type
arch/arm/boot/dts/am437x-cm-t43.dts | 2 +-
arch/arm/boot/dts/am437x-gp-evm.dts | 2 +-
arch/arm/boot/dts/am437x-sk-evm.dts | 2 +-
arch/arm/boot/dts/am43x-epos-evm.dts | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2018-04-20 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 11:38 Peter Ujfalusi [this message]
2018-04-20 11:38 ` [PATCH 1/4] ARM: dts: am437x-gp-evm: " Peter Ujfalusi
2018-04-20 11:38 ` [PATCH 2/4] ARM: dts: am437x-cm-t43: " Peter Ujfalusi
2018-04-20 11:38 ` [PATCH 3/4] ARM: dts: am437x-epos-evm: " Peter Ujfalusi
2018-04-20 11:38 ` [PATCH 4/4] ARM: dts: am437x-sk-evm: " Peter Ujfalusi
2018-04-23 10:31 ` [PATCH 0/4] ARM: dts: am437x boards: " Keerthy
2018-05-01 15:33 ` Tony Lindgren
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=20180420113822.17577-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®