public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	Govindraj <govindraj.ti@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Pandita, Vikram" <vikram.pandita@ti.com>,
	"Raja, Govindraj" <govindraj.raja@ti.com>
Subject: Re: [PATCHv3 0/3] OMAP UART: Adding support for omap-serial driver.
Date: Wed, 25 Nov 2009 01:06:10 -0600	[thread overview]
Message-ID: <4B0CD762.70707@lixom.net> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402543D7ED2@dbde02.ent.ti.com>

G, Manjunath Kondaiah wrote:
>>> You should allow both of them to be enabled at the same time, so the
>>> same
>>> kernel can for example be booted on a ZOOM2 with debug board
>>> attached
>>> (8250 on GPMC), or on a beagle/overo board.
>>>
>>> Making them exclusive would be a step backwards.
>>>       
>> More so, selecting both config option really shouldn't break 
>> the build. If one expect a build break because only one of 
>> the options can be enabled then clearly the dependency should 
>> be used so that user can select only one option at a time.
>>     
>
> Ack. There should be dependency in Kconfig so that user can select
> either 8250 console(through Quad-uart for zoom2/zoom3) or OMAP-serial
> Console(through OMAP UART's).
>   

No. The drivers MUST handle co-existing. You can have a bunch of drivers 
configured to be _potential_ consoles, which one will end up being used 
depends on, among other things, the bootargs. But it should be allowed 
to configure both 8250 and omap-serial at the same time.


-Olof

  reply	other threads:[~2009-11-25  7:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <35552.192.168.10.88.1256713953.squirrel@dbdmail.itg.ti.com>
2009-11-13  6:53 ` [PATCHv3 0/3] OMAP UART: Adding support for omap-serial driver Govindraj.R
2009-11-20  9:51   ` Govindraj
2009-11-23 17:05     ` Olof Johansson
2009-11-24  9:34       ` G, Manjunath Kondaiah
2009-11-24 17:21         ` Olof Johansson
2009-11-25  6:35           ` Shilimkar, Santosh
2009-11-25  7:02             ` G, Manjunath Kondaiah
2009-11-25  7:06               ` Olof Johansson [this message]
2009-11-25 17:40                 ` Tony Lindgren
2009-11-25 18:05                   ` Kevin Hilman
2009-11-23 17:11     ` Olof Johansson
2009-11-23 22:19       ` Kevin Hilman

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=4B0CD762.70707@lixom.net \
    --to=olof@lixom.net \
    --cc=govindraj.raja@ti.com \
    --cc=govindraj.ti@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manjugk@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.com \
    --cc=vikram.pandita@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox