From: Alan Cox <alan@linux.intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Feng Tang <feng.tang@intel.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, greg@kroah.com,
x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH v3 4/4] x86, earlyprintk: add hsu early console for Intel Medfield platform
Date: Thu, 23 Sep 2010 11:08:05 +0100 [thread overview]
Message-ID: <20100923110805.2fe5b2a9@linux.intel.com> (raw)
In-Reply-To: <20100921162627.GA21459@dumpdata.com>
> Is there a link to a PDF of the device in question?
Not that I know of at least so far.
> > + */
> > +#define HSU_PORT2_PADDR 0xffa28180
>
> Is it _always_ that address?
Yes.
> > +
> > +static void __iomem *phsu;
> > +
> > +void hsu_early_console_init(void)
> > +{
> > + u8 lcr;
> > +
> > + phsu = (void
> > *)set_fixmap_offset_nocache(FIX_EARLYCON_MEM_BASE,
> > +
> > HSU_PORT2_PADDR); +
> > + /* Disable FIFO */
> > + writeb(0x0, phsu + UART_FCR);
>
> No detection? What happens if you don't have the device (say in
> production it gets removed) and we try to use earlyprintk=hsu? Won't
> we have some trouble?
Same as if you try and use the other serial console drivers that way.
It's a bit tricky to do much about because to be sure you've got this
stuff you need to have done a whole ton of work which then makes the
early console pointless.
>
> > +
> > + /* Set to default 115200 bps, 8n1 */
>
> Is that OK? Should there be some parsing of the baudrate data?
For a serial console yes - for an early console robustness is
everything, and its an embedded development environment so fixed
configuration really isn't a problem.
next prev parent reply other threads:[~2010-09-23 10:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 7:08 [PATCH v3 0/4] Enabling patches of 2 early consoles for Intel MID platforms Feng Tang
2010-09-13 7:08 ` [PATCH v3 1/4] x86, mrst: make mrst_identify_cpu() inlne inside mrst.h Feng Tang
2010-09-14 13:43 ` Alan Cox
2010-09-14 17:57 ` Ingo Molnar
2010-09-14 19:50 ` Alan Cox
2010-09-15 8:24 ` Ingo Molnar
2010-09-13 7:08 ` [PATCH v3 2/4] x86: add two helper macros for fixed address mapping Feng Tang
2010-10-08 10:52 ` [tip:x86/mrst] x86: Add " tip-bot for Feng Tang
2010-09-13 7:08 ` [PATCH v3 3/4] x86, earlyprintk: add earlyprintk for Intel Moorestown platform Feng Tang
2010-10-08 10:53 ` [tip:x86/mrst] x86, earlyprintk: Add " tip-bot for Feng Tang
2010-09-13 7:08 ` [PATCH v3 4/4] x86, earlyprintk: add hsu early console for Intel Medfield platform Feng Tang
2010-09-21 16:26 ` Konrad Rzeszutek Wilk
2010-09-23 10:08 ` Alan Cox [this message]
2010-10-08 10:53 ` [tip:x86/mrst] x86, earlyprintk: Add " tip-bot for Feng Tang
2010-09-13 8:40 ` [PATCH v3 0/4] Enabling patches of 2 early consoles for Intel MID platforms Ingo Molnar
2010-09-13 16:59 ` Greg KH
2010-09-13 18:43 ` Ingo Molnar
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=20100923110805.2fe5b2a9@linux.intel.com \
--to=alan@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=greg@kroah.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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.