From: Greg KH <gregkh@linuxfoundation.org>
To: "Mukesh, Savaliya" <msavaliy@codeaurora.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Akash Asthana <akashast@codeaurora.org>,
saravanak@google.com, sspatil@google.com, tkjos@google.com,
linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6] serial: msm_geni_serial_console : Add Earlycon support
Date: Wed, 8 Jul 2020 17:40:28 +0200 [thread overview]
Message-ID: <20200708154028.GC715257@kroah.com> (raw)
In-Reply-To: <c2752c91-b203-4224-9ddf-1e5a03b6488b@codeaurora.org>
On Wed, Jul 08, 2020 at 08:06:52PM +0530, Mukesh, Savaliya wrote:
>
> On 6/24/2020 1:19 AM, Bjorn Andersson wrote:
> > On Mon 22 Jun 03:08 PDT 2020, Akash Asthana wrote:
> >
> > > From: Mukesh Kumar Savaliya <msavaliy@codeaurora.org>
> > >
> > > This change enables earlyconsole support as static driver for geni
> > > based UART. Kernel space UART console driver will be generic for
> > > console and other usecases of UART.
> > >
> > Is this hardware different from the qcom,geni-debug-uart which we
> > already have EARLYCON support for?
> >
> > Why is this a separate driver?
>
> The Hardware is same, but for the Generic kernel image we are using
> downstream driver which can't be a static compiled driver.
Why not? Why not fix that?
> The same driver file has 1.earlyconsole, 2.kernel console and 3.HSUART
> driver parts.
>
> To make Generic image, 2 and 3 are internal downstream driver and 1st one i
> am trying to get upstreamed, so that can be pulled into the ACK.
That has nothing to do with us, please do it correctly so that everyone
benifits.
> The one with the qcom,genu-debug-uart is not being used for our products.
So we can just delete it from the tree?
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-08 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 10:08 [PATCH V6] serial: msm_geni_serial_console : Add Earlycon support Akash Asthana
2020-06-23 19:49 ` Bjorn Andersson
2020-07-08 14:36 ` Mukesh, Savaliya
2020-07-08 15:40 ` Greg KH [this message]
2020-07-05 6:10 ` kernel test robot
2020-07-05 6:10 ` kernel test robot
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=20200708154028.GC715257@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akashast@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=msavaliy@codeaurora.org \
--cc=saravanak@google.com \
--cc=sspatil@google.com \
--cc=tkjos@google.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 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.