From: Sudeep Holla <sudeep.holla@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: mps2: use list instead of tuple for uart interrupts
Date: Tue, 22 Jan 2019 13:51:05 +0000 [thread overview]
Message-ID: <20190122135105.GB18606@e107155-lin> (raw)
In-Reply-To: <3de06852-597b-06dd-a2d1-8b0830a7869f@arm.com>
On Tue, Jan 22, 2019 at 01:32:26PM +0000, Vladimir Murzin wrote:
> On 1/22/19 11:55 AM, Sudeep Holla wrote:
> > On Mon, Jan 21, 2019 at 10:35:39AM +0000, Vladimir Murzin wrote:
> >> MPS2 UART requires dedicated interrupts for RX, TX and overflow, which
> >> obviously should be expressed as a list. Current form uses tuple and
> >> it has worked so far because NVIC has interrupt-cells equal to 1.
> >
> > Applied for v5.1
> >
> > Just saw couple of other instances that can be fixed to elsewhere in
> > vexpress DTS files. Will post it soon with your reported by(though
> > you didn't report them directly but this patch made me look around)
>
> Thanks!
>
> Now I'm wondering if it is something dtc can warn about?
>
Not sure if it's already in place at different warning level.
I generally try W=1 which itself produces quite a lot of warning, but
yes good if this can be detected by compiler.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-22 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 10:35 [PATCH] ARM: dts: mps2: use list instead of tuple for uart interrupts Vladimir Murzin
2019-01-22 11:55 ` Sudeep Holla
2019-01-22 13:32 ` Vladimir Murzin
2019-01-22 13:51 ` Sudeep Holla [this message]
2019-01-22 17:14 ` Vladimir Murzin
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=20190122135105.GB18606@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vladimir.murzin@arm.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