linux-kernel - Re: How to structure an SPI UART driver?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1176982391.4906.4.camel@diimka.dev.rtsoft.ru>
Date:	Thu, 19 Apr 2007 15:33:11 +0400
From:	dmitry pervushin <dpervushin@...il.com>
To:	Zik Saleeba <zik@...zak.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to structure an SPI UART driver?

On Чтв, 2007-04-19 at 17:45 +1000, Zik Saleeba wrote:
> I'm looking for a little advice on writing a driver for the Phillips
> sc16is752 SPI UART chip. I've written drivers before but I'm having a
> problem with this one. Since this driver is both an SPI driver and a
> UART driver I'm unclear on whether it should register with
> spi_register_driver() or uart_register_driver(), or both, or do
> something completely different. I'm not clear on how to play nicely
> with both subsystems.
It should call both. Think about your driver as the middleware -- bottom
half is SPI driver (and uses spi_xxx calls to interact with hardware),
and upper half is UART (and uses uart_xxx calls to provide inerface). 
> Any hints?
...and welcome to spi-devel mailing list, spi-devel-general@...ts.sourceforge.net
> Cheers,
> Zik
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/