From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Johannes Thumshirn" <johannes.thumshirn@men.de>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"Thomas Schnuerer" <thomas.schnuerer@men.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jslaby@suse.cz>
Subject: Re: [PATCH] tty: serial: Add driver for MEN's 16z135 High Speed UART.
Date: Thu, 17 Apr 2014 14:08:28 +0400 [thread overview]
Message-ID: <1397729308.556196520@f417.i.mail.ru> (raw)
In-Reply-To: <1397727894-10123-1-git-send-email-johannes.thumshirn@men.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1536 bytes --]
Thu, 17 Apr 2014 11:44:54 +0200 Ð¾Ñ Johannes Thumshirn <johannes.thumshirn@men.de>:
> Add driver for MEN's 16z135 High Speed UART.
>
> The 16z135 is a memory mapped UART Core on an MCB FPGA and has 1024 byte
> deep FIFO buffers for the RX and TX path. It also has configurable FIFO
> fill level IRQs and data copied to and from the hardware has to be
> acknowledged.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@men.de>
> ---
...
> +static int men_z135_probe(struct mcb_device *mdev,
> + const struct mcb_device_id *id)
> +{
> + struct men_z135_port *uart;
> + struct resource *mem;
> + struct device *dev;
> + int err;
> +
> + dev = &mdev->dev;
> +
> + uart = devm_kzalloc(dev, sizeof(struct men_z135_port), GFP_KERNEL);
> + if (!uart)
> + return -ENOMEM;
> +
> + uart->rxbuf = (unsigned char *)__get_free_page(GFP_KERNEL);
> + if (!uart->rxbuf)
> + return -ENOMEM;
> +
> + mem = &mdev->mem;
> +
> + mcb_set_drvdata(mdev, uart);
> +
> + uart->port.uartclk = MEN_Z135_BASECLK * 16;
> + uart->port.fifosize = MEN_Z135_FIFO_SIZE;
> + uart->port.iotype = UPIO_MEM;
> + uart->port.ops = &men_z135_ops;
> + uart->port.irq = mcb_get_irq(mdev);
> + uart->port.iotype = UPIO_MEM;
> + uart->port.flags = UPF_BOOT_AUTOCONF | UPF_IOREMAP;
> + uart->port.line = line++;
So, every time a module is loaded/unloaded and loaded again,
you increase the line number?
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-04-17 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 9:44 Johannes Thumshirn
2014-04-17 10:08 ` Alexander Shiyan [this message]
2014-04-17 10:50 ` One Thousand Gnomes
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=1397729308.556196520@f417.i.mail.ru \
--to=shc_work@mail.ru \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.thumshirn@men.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=thomas.schnuerer@men.de \
/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®