From: Andy Duan <fugang.duan@nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: RE: [EXT] [RFC PATCH 1/2] arm64: dts: imx8mm: Fix the ENET interrupts order
Date: Wed, 19 Aug 2020 01:36:37 +0000 [thread overview]
Message-ID: <AM8PR04MB731542B054055078AA73F97EFF5D0@AM8PR04MB7315.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200818210529.5884-1-festevam@gmail.com>
From: Fabio Estevam <festevam@gmail.com> Sent: Wednesday, August 19, 2020 5:05 AM
> Hi Fugang,
>
> Could you please help review this RFC series?
>
> My understanding is that the i.MX8M class of products are derived from
> i.MX7 from an ENET IRQ mapping perspective. (i.MX8QXP also uses the same
> i.MX7 mapping by the way). The Reference Manual also seems to indicate the
> same, but the ENET IRQ naming differs a bit between the
> i.MX7 and i.MX8MM RM's.
>
> If this is correct, then I plan to also fix i.MX8MQ, i.MX8MN and i.MX8MP dtsi
> files.
>
> My initial goal was to add the pps irq (patch 2/2), but then I noticed the
> potential irq mismatch and now it is a two patch series.
>
> Thanks
It doesn't matter, since there three irq share the same irq handler, and irq handler distinguish
Irq by checking register event, so there have no explicit mapping for the three irqs, so we never
see problem. But for the fourth irq that is required for the last one, which is for pps, not for ptp4l.
Regards,
Fugang
_______________________________________________
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:[~2020-08-19 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 21:05 [RFC PATCH 1/2] arm64: dts: imx8mm: Fix the ENET interrupts order Fabio Estevam
2020-08-18 21:05 ` [RFC PATCH 2/2] arm64: dts: imx8mm: Describe the ENET pps interrupt Fabio Estevam
2020-08-19 1:43 ` [EXT] " Andy Duan
2020-08-19 1:36 ` Andy Duan [this message]
2020-08-19 1:47 ` [EXT] [RFC PATCH 1/2] arm64: dts: imx8mm: Fix the ENET interrupts order Fabio Estevam
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=AM8PR04MB731542B054055078AA73F97EFF5D0@AM8PR04MB7315.eurprd04.prod.outlook.com \
--to=fugang.duan@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=shawnguo@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 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.