linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: Driver for SPI-based 8250 serial port
Date: Wed, 05 Sep 2012 18:29:33 +0200	[thread overview]
Message-ID: <50477DED.602@mind.be> (raw)
In-Reply-To: <20120905141218.7556f902@pyramind.ukuu.org.uk>

On 09/05/12 15:12, Alan Cox wrote:
>> >  - Should I add a UPIO_SPI to the global I/O types, or should I override the
>> >  serial_in/serial_out functions in struct plat_serial8250_port?
> I am not sure you'll make the 8250 driver handle the device because I
> suspect a lot of the serial_in/serial_out calls occur with interrupts
> disabled on the assumption that they are basically atomic fast operations.

  Argh, that's right.

  So it will be a completely new driver then.  Using the tty layer directly seems
to be a good suggestion: it looks like the uart layer (like the 8250 driver) is
carrying a lot of cruft for supporting all those quirks in the different devices.

  ifx6x60 looks like a good source of inspiration.


  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-09-05 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 12:47 Driver for SPI-based 8250 serial port Arnout Vandecappelle
2012-09-05 13:12 ` Alan Cox
2012-09-05 16:29   ` Arnout Vandecappelle [this message]

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=50477DED.602@mind.be \
    --to=arnout@mind.be \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-serial@vger.kernel.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).