From: Linus Walleij <linus.walleij@linaro.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/2] misc: aspeed: Add Aspeed UART routing control driver.
Date: Tue, 4 Sep 2018 23:55:50 +0200 [thread overview]
Message-ID: <CACRpkdamHdGH9bANugQchYLWFS_mde6MmcbvBgcG-hrhvGVFWQ@mail.gmail.com> (raw)
In-Reply-To: <20180904202018.198707-2-osk@google.com>
On Tue, Sep 4, 2018 at 10:20 PM Oskar Senft <osk@google.com> wrote:
> This driver adds sysfs files that allow the BMC userspace to configure
> how UARTs and physical serial I/O ports are routed.
>
> Tested: Checked correct behavior (both read & write) on TYAN S7106
> board by manually changing routing settings and confirming that bits
> flow as expected. Tested for UART1 and UART3 as this board doesn't have
> the other UARTs wired up in a testable way.
>
> Signed-off-by: Oskar Senft <osk@google.com>
After reading some other messages about this I realize it's not very
much you can do with the standard frameworks and you definately
need something like this. Not like I have any better idea.
Arnd and Greg are misc maintainers so not you will need to
talk to them.
I would opt to put it in drivers/soc/aspeed though.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-09-04 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 20:20 Aspeed UART routing driver Oskar Senft
2018-09-04 20:20 ` [PATCH 1/2] misc: aspeed: Add Aspeed UART routing control driver Oskar Senft
2018-09-04 21:55 ` Linus Walleij [this message]
2018-09-05 0:15 ` Andrew Jeffery
2018-09-05 0:19 ` Oskar Senft
2018-09-05 6:06 ` Linus Walleij
2018-09-05 13:45 ` Oskar Senft
2018-09-05 19:27 ` Linus Walleij
2018-09-04 20:20 ` [PATCH 2/2] arch: arm: boot: dts: aspeed: Add UART routing driver to Aspeed G5 DTS Oskar Senft
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=CACRpkdamHdGH9bANugQchYLWFS_mde6MmcbvBgcG-hrhvGVFWQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-aspeed@lists.ozlabs.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).