linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: at91: remove at91_register_uart_fns and headers
Date: Wed, 11 Apr 2012 13:37:50 +0200	[thread overview]
Message-ID: <4F856D0E.5040802@atmel.com> (raw)
In-Reply-To: <CAFumwP38ghv91gwZ55pQeDDD67_t+61pLqBkvX8wzZk5R-3z5w@mail.gmail.com>

On 04/08/2012 11:55 PM, Andrew Victor :
> hi,
> 
>> Yeah, as far as I know, nobody ever used this functionality on AVR32.
>> In fact, I can't even think of a reason to use it.
>>
>> But I seem to recall submitting a patch to remove this functionality a
>> long time ago, and it was struck down. I don't remember the reason,
>> but there's a chance it might still be valid.
> 
> Some of the SAN People / Multenet AT91RM9200 boards needed it....
> We needed to use GPIO pins for some of the modem-control signals -
> couldn't use the standard pins since the alternate pin function was
> being used.
> 
> Regards,
>  Andrew Victor

Hi Andrew,

Well if it is of some interest on your side, I am in favor of keeping
this feature. It is not a so big amount of code and seems quite easy to
maintain...

Thanks a lot to all for your feedback anyway.

Cheers,
-- 
Nicolas Ferre

  reply	other threads:[~2012-04-11 11:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 16:02 [PATCH RFC] ARM: at91: remove at91_register_uart_fns and headers Joachim Eastwood
2012-04-06 16:19 ` Joachim Eastwood
2012-04-08 18:09 ` Hans-Christian Egtvedt
2012-04-08 21:21   ` Håvard Skinnemoen
2012-04-08 21:55     ` Andrew Victor
2012-04-11 11:37       ` Nicolas Ferre [this message]
2012-04-11 16:35         ` Joachim Eastwood

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=4F856D0E.5040802@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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).