From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 1/5] ARM: OMAP2+: omap_hwmod: Add support for earlycon Date: Wed, 18 Jan 2017 09:00:34 -0800 Message-ID: <20170118170033.GD7403@atomide.com> References: <20170117040336.21700-1-lokeshvutla@ti.com> <20170117040336.21700-2-lokeshvutla@ti.com> <20170117232310.GX7403@atomide.com> <88830967-6e83-33fc-8a1c-d776fd694e2f@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <88830967-6e83-33fc-8a1c-d776fd694e2f-l0cyMroinI0@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Lokesh Vutla Cc: Linux OMAP Mailing List , Device Tree Mailing List , Rob Herring , Tero Kristo , Sekhar Nori , Vignesh R , Nishanth Menon List-Id: devicetree@vger.kernel.org * Lokesh Vutla [170117 19:50]: > > > On Wednesday 18 January 2017 04:53 AM, Tony Lindgren wrote: > > * Lokesh Vutla [170116 20:06]: > >> Hwmod core tries to reset and idles each IP that is registered with hwmod. > >> In case of earlycon, that specific uart IP cannot be reset or keep it in > >> idle state else earlycon hangs once hwmod resets that uart IP. So add support > >> to not reset uart that is being used as earlycon only if CONFIG_SERIAL_EARLYCON > >> is enabled. > > > > Nice :) > > > > I guess this has no dependency to SERIAL_OMAP vs 8250_OMAP selection? > > Unfortunately SERIAL_OMAP does not support earlycon yet. As I mentioned > in my cover letter, I verified this series only with 8250_OMAP. OK. So just to understand why it would not work with omap-serial, do we need something implemented in drivers/tty/serial/earlycon.c for non 8250 drivers to make it work? Or are there other dependencies? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html