linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: christian pellegrin <chripell-VaTbYqLCNhc@public.gmane.org>
Cc: greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org,
	linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org
Subject: Re: [PATCH 3/3] max3100: adds console support for MAX3100
Date: Sun, 21 Mar 2010 09:28:48 -0700	[thread overview]
Message-ID: <201003210928.48937.david-b@pacbell.net> (raw)
In-Reply-To: <cabda6421003210047i1d4545aasf8969bb70d48ceb9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sunday 21 March 2010, christian pellegrin wrote:
> > Anybody know the right thing to do here?

when to register consoles is a general mess.  I've seeen some
success in having it be board-specific data, at the level of
"port 3 should be a console ... or in this case, maybe having
platform data say which chip.

After all, board docs probably assign numbers to each of the
external connetors, and say "#1 is normally the onsole" (or
maybe #0, #3, etc).


But it's still kind of chaotic trying to set things up so that
for example $3 becomes /dev/ttyS3" and so forth.  Especially if
your chip has six serial ports but several of them aren't wired
up (and so should not get published to userspace even if they do
get autodetected...  (Heck, the controller may exist, but the
unavailability may as easily be "those pins are routed to some
other peripheral" as ""those pins aren't wired up to RS232 level
shifters or a DB9/RJ45/... connector.

.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

  parent reply	other threads:[~2010-03-21 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  8:39 [PATCH 0/3] max3100: improvements christian pellegrin
     [not found] ` <cabda6421003190139h344bc172h3556fca78e4b25cb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-19  8:38   ` [PATCH 1/3] max3100: added raise_threaded_irq Christian Pellegrin
2010-03-19 17:48     ` Grant Likely
2010-03-21  7:31       ` christian pellegrin
2010-03-19  8:39   ` [PATCH 2/3] max3100: moved to threaded interrupt Christian Pellegrin
2010-03-19 17:58     ` Grant Likely
2010-03-21  7:34       ` christian pellegrin
2010-03-19  8:39   ` [PATCH 3/3] max3100: adds console support for MAX3100 Christian Pellegrin
2010-03-19 19:31     ` Grant Likely
2010-03-21  7:47       ` christian pellegrin
     [not found]         ` <cabda6421003210047i1d4545aasf8969bb70d48ceb9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-21 16:28           ` David Brownell [this message]
2010-03-22  1:31     ` Feng Tang
2010-03-22  7:03       ` christian pellegrin

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=201003210928.48937.david-b@pacbell.net \
    --to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=chripell-VaTbYqLCNhc@public.gmane.org \
    --cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
    --cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).