[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181113144209.GB4557@dragon>
Date: Tue, 13 Nov 2018 22:42:11 +0800
From: Shawn Guo <shawnguo@...nel.org>
To: Martin Kaiser <martin@...ser.cx>
Cc: Sascha Hauer <s.hauer@...gutronix.de>,
Clément Péron <peron.clem@...il.com>,
Vladimir Zapolskiy <vladimir_zapolskiy@...tor.com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
NXP Linux Team <linux-imx@....com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: dts: i.MX25: add the clocks for the EPIT blocks
On Mon, Nov 05, 2018 at 10:12:30AM +0100, Martin Kaiser wrote:
> Hi,
>
> Thus wrote Shawn Guo (shawnguo@...nel.org):
>
> > On Thu, Nov 01, 2018 at 06:32:47PM +0100, Martin Kaiser wrote:
> > > The i.MX25 contains two EPIT (Enhanced Periodic Interrupt Timer)
> > > function blocks. Add their ipg and per clocks to the device tree.
>
> > > Signed-off-by: Martin Kaiser <martin@...ser.cx>
>
> > Are these EPIT devices actually used in upstream kernel, or just
> > somewhere else?
>
> Until I saw Vladimir's mail this morning, I wasn't aware of any mainline
> driver that's using the EPIT devices. I found that the clocks are
> missing when I tried to use EPIT with a company-internal driver that's
> not suitable for mainline integration.
>
> Still, I think that merging this patch does no harm. If the EPIT devices
> are present in the DT, we should add all resources they're using.
Agreed. I will be happy to apply the patch if I can get an ACK from
Clément saying this works with his driver in upstreaming.
Shawn
Powered by blists - more mailing lists