Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: ashlesha@kenati.com
Cc: linux-mips@linux-mips.org
Subject: Re: serial console: platform_device
Date: Tue, 05 Dec 2006 23:46:55 +0300	[thread overview]
Message-ID: <4575DABF.2000604@ru.mvista.com> (raw)
In-Reply-To: <1165351710.6871.34.camel@sandbar.kenati.com>

Hello.

Ashlesha Shintre wrote:

>>>3) control goes into the serial8250_probe function and assigns values
>>>from the plat_serial8250_port encm3_via_uart_data to the port..so what
>>>is the basic difference between registration of "probe device" versus

>>>"platform bus" devices in the 2.6 kernel?

>>    I'm not sure I follow you here.

> What I meant was, what was the basis for the implementation of
> platform_device and platform_init functions in 2.6?

    This is a convenient way to registers the various SoC and on-board devices 
residing on the busses that can't be scanned like ISA/LPC/whatever (and unlike 
PCI, for example).

> By my understanding the way it worked in 2.4 was by the device probing
> functions that would allocate memory, io ports etc..

    Basically, you don't need to probe for device which you *know* is there, 
you just need to tell the driver where it is.

> m working on making the changes you suggested --

> without the addition of the platform_device and other structures, the

    I meant that you *only* need struct plat_serial8250_port, and not 
platform_device.

> serial console is never detected -- I never get a msg at boot time that
> reads 

> serial8250: ttyS0 at I/O 0x3f8 (irq = whatever) is a 16550A

> so I think i might need these routines

> Also, the Southbridge interrupts are assigned interrupt number:
> AU1000_GPIO_0..and I have included this as below:

    Ah, I forgot to mention that if your UART is a part of the south bridge, 
its IRQ number is _4_ on the integrated 8259 interrupt controller. I'm sure 
that AU1000_GPIO_0 is the cascaded interrupt request from 8259, not the UART's 
own IRQ...

>>static struct plat_serial8250_port encm3_via_uart_data[] = {
>>                {
>>                        .mapbase        = 0x3f8,
>>                        .irq            = AU1000_GPIO_0,

    So, this is wrong. You need to specify to what platform IRQ 8259's IRQ4 
gets routed here.

> Thanks again!
> Ashlesha.

WBR, Sergei

  reply	other threads:[~2006-12-05 20:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 19:23 serial console: platform_device Ashlesha Shintre
2006-12-05 19:42 ` Sergei Shtylyov
2006-12-05 20:48   ` Ashlesha Shintre
2006-12-05 20:46     ` Sergei Shtylyov [this message]
2006-12-06  0:30       ` Ashlesha Shintre
2006-12-06 12:59         ` Sergei Shtylyov
2006-12-06 19:49           ` Ashlesha Shintre
2006-12-06 19:54             ` Sergei Shtylyov
2006-12-07  0:13               ` Cant analyze prologue code Ashlesha Shintre
2006-12-07  1:37                 ` Atsushi Nemoto
2006-12-07  3:39                   ` Ashlesha Shintre
2006-12-07  4:13                     ` Atsushi Nemoto
     [not found]                       ` <1165534711.6512.10.camel@sandbar.kenati.com>
     [not found]                         ` <20061208.101112.108306293.nemoto@toshiba-tops.co.jp>
2006-12-08  2:01                           ` Serial 8250 driver registration: Ashlesha Shintre
2006-12-08 12:59                             ` Sergei Shtylyov

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=4575DABF.2000604@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=ashlesha@kenati.com \
    --cc=linux-mips@linux-mips.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