linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Tai <james.tai@realtek.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-realtek-soc@lists.infradead.org" 
	<linux-realtek-soc@lists.infradead.org>
Subject: RE: [PATCH] arm64: dts: realtek: Add Realtek rtd1619 and mjolnir
Date: Sat, 23 Nov 2019 08:51:52 +0000	[thread overview]
Message-ID: <bc9c923789fe4f0586df3d2051e5721d@realtek.com> (raw)
In-Reply-To: <6d44e7f8-1ae5-ed3d-ac3c-0ee7903d660b@suse.de>

Hi Andreas,

> >> back RTD1619 irq mux patches from my irqchip v4 series [1].
> >>
> > It is code wrong. The UR0 should remove from "irq-rtd16xx.h".
> 
> Actually, I just tested that UR0 works! (rev A01) So we shouldn't remove it from
> the irqchip driver, given the mapping changes requested for v5.

The UR0 has been removed from the RTD1619 specification. 
I'll check it again.


Regards,
James



      reply	other threads:[~2019-11-23  8:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  8:00 [PATCH] arm64: dts: realtek: Add Realtek rtd1619 and mjolnir James Tai
2019-11-06  8:28 ` Andreas Färber
2019-11-08 15:36   ` James Tai
2019-11-08 17:17     ` Andreas Färber
2019-11-11  2:58       ` James Tai
2019-11-15  1:08         ` Andreas Färber
2019-11-17 15:39           ` James Tai
2019-11-22  9:43             ` Marc Zyngier
2019-11-22 12:48               ` Andreas Färber
2019-11-23  8:40                 ` James Tai
2019-11-11  3:09       ` Andreas Färber
2019-11-19  9:11     ` Andreas Färber
2019-11-20  7:58       ` James Tai
2019-11-22  3:03         ` Andreas Färber
2019-11-23  8:51           ` James Tai [this message]

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=bc9c923789fe4f0586df3d2051e5721d@realtek.com \
    --to=james.tai@realtek.com \
    --cc=afaerber@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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 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).