From: Al Cooper <alcooperx@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Al Cooper <alcooperx@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: [PATCH v7 0/2] 8250: Add driver for Broadcom UART
Date: Thu, 25 Mar 2021 14:52:54 -0400 [thread overview]
Message-ID: <20210325185256.16156-1-alcooperx@gmail.com> (raw)
v7 - Change Kconfig for SERIAL_8250_BCM7271 from "bool" to "tristate"
so the driver can be built as a module.
v6 - A few more changes based on requests from Greg Kroah-Hartman
- Don't save the debugfs file handle in priv because it was
never used.
- Change all dev_info() messages to dev_dbg() messages.
- Fix warnings from the kernel test robot
- Use --base with "git format-patch"
- Fixes in the .yaml file based on requests from Rob Herring
- Change "oneOf" to "minItems: 1".
- Reference serial.yaml instead of using "$nodname".
- Add missing newline.
v5 - Changes based on requests from Greg Kroah-Hartman
- Move sysfs stats to debugfs.
- Merge the .h file into the .c file.
- Convert "flags" with only one flag to bool
- Remove most dev_dbg() messages. Some can be replaced by using
ftrace and some would cause a crash if the driver was used
for the console.
v4 - Fix MAINTAINERS
- Make all changes requested by Jira Slaby. The only functional
change was to handle errors returned by brcmuart_arbitration()
in brcmuart_resume().
v3 - remove "disable_dma" module param because it can be done
by modifying the device tree node instead. Reduce size by
removing some debug fuctionality that was no longer used.
- Fix error from yaml compiler in bindings
v2 - remove the patch that modified 8250_of.c to keep it from
registering before this driver when this driver was deferred
as it was getting it's "clocks". This was fixed by changing
the Device Tree entry to remove "clock-frequency". This results
in both drivers getting "clocks" and getting same the deferral.
Al Cooper (2):
dt-bindings: Add support for the Broadcom UART driver
serial: 8250: Add new 8250-core based Broadcom STB driver
.../bindings/serial/brcm,bcm7271-uart.yaml | 95 ++
MAINTAINERS | 8 +
drivers/tty/serial/8250/8250_bcm7271.c | 1202 +++++++++++++++++
drivers/tty/serial/8250/Kconfig | 10 +
drivers/tty/serial/8250/Makefile | 1 +
5 files changed, 1316 insertions(+)
create mode 100644 Documentation/devicetree/bindings/serial/brcm,bcm7271-uart.yaml
create mode 100644 drivers/tty/serial/8250/8250_bcm7271.c
base-commit: e138138003eb3b3d06cc91cf2e8c5dec77e2a31e
--
2.17.1
next reply other threads:[~2021-03-25 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 18:52 Al Cooper [this message]
2021-03-25 18:52 ` [PATCH v7 1/2] dt-bindings: Add support for the Broadcom UART driver Al Cooper
2021-03-25 18:52 ` [PATCH v7 2/2] serial: 8250: Add new 8250-core based Broadcom STB driver Al Cooper
2021-03-26 14:18 ` [PATCH v7 0/2] 8250: Add driver for Broadcom UART Greg Kroah-Hartman
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=20210325185256.16156-1-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=robh+dt@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).