mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Victor <andrew@sanpeople.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] atmel_serial: Kill at91_register_uart_fns
Date: 28 Sep 2006 11:21:55 +0200	[thread overview]
Message-ID: <1159435315.23157.73.camel@fuzzie.sanpeople.com> (raw)
In-Reply-To: <11593762852950-git-send-email-hskinnemoen@atmel.com>

hi Haavard,

> at91_register_uart_fns has no users as far as I can see. Let's get
> rid of it.

No.  It is being used.

This interface is used to register board-specific functions that can be
use to control the serial port modem-control lines.

For example, the AT91RM9200 only provides the full modem-control signals
on USART1.  If you need the modem-control signals for any of the other
ports you need to drive some of the GPIO pins manually.  So you need
this hook back into your board-specific file to do that.


Regards,
  Andrew Victor



  reply	other threads:[~2006-09-28  9:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 16:57 [PATCH 0/8] Rename at91_serial driver as atmel_serial Haavard Skinnemoen
2006-09-27 16:57 ` [PATCH 1/8] at91_serial -> atmel_serial: at91rm9200_usart.h Haavard Skinnemoen
2006-09-27 16:57   ` [PATCH 2/8] at91_serial -> atmel_serial: at91_serial.c Haavard Skinnemoen
2006-09-27 16:58     ` [PATCH 3/8] at91_serial -> atmel_serial: Kconfig symbols Haavard Skinnemoen
2006-09-27 16:58       ` [PATCH 4/8] at91_serial -> atmel_serial: Platform device name Haavard Skinnemoen
2006-09-27 16:58         ` [PATCH 5/8] at91_serial -> atmel_serial: Public definitions Haavard Skinnemoen
2006-09-27 16:58           ` [PATCH 6/8] at91_serial -> atmel_serial: Internal names Haavard Skinnemoen
2006-09-27 16:58             ` [PATCH 7/8] serial: Rename PORT_AT91 -> PORT_ATMEL Haavard Skinnemoen
2006-09-27 16:58               ` [PATCH 8/8] atmel_serial: Kill at91_register_uart_fns Haavard Skinnemoen
2006-09-28  9:21                 ` Andrew Victor [this message]
2006-09-28  9:38                   ` Haavard Skinnemoen
2006-09-28 11:14                     ` Andrew Victor
2006-09-28 11:51                       ` Haavard Skinnemoen
2006-09-28 11:56                         ` Andrew Victor
2006-09-28 17:02                           ` Sam Ravnborg
2006-09-28  9:03               ` [PATCH 7/8] serial: Rename PORT_AT91 -> PORT_ATMEL Andrew Victor
2006-09-28  9:02             ` [PATCH 6/8] at91_serial -> atmel_serial: Internal names Andrew Victor
2006-09-28  8:54           ` [PATCH 5/8] at91_serial -> atmel_serial: Public definitions Andrew Victor
2006-09-28  9:24             ` Haavard Skinnemoen
2006-09-28  9:22               ` Andrew Victor
2006-09-28  8:35         ` [PATCH 4/8] at91_serial -> atmel_serial: Platform device name Andrew Victor
2006-09-28 12:55         ` Haavard Skinnemoen
2006-09-28  8:34       ` [PATCH 3/8] at91_serial -> atmel_serial: Kconfig symbols Andrew Victor
2006-09-28  8:54         ` Haavard Skinnemoen
2006-09-28  8:50           ` Andrew Victor
2006-09-28  8:22     ` [PATCH 2/8] at91_serial -> atmel_serial: at91_serial.c Andrew Victor
2006-09-28  8:20   ` [PATCH 1/8] at91_serial -> atmel_serial: at91rm9200_usart.h Andrew Victor

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=1159435315.23157.73.camel@fuzzie.sanpeople.com \
    --to=andrew@sanpeople.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®