From: Ramon Fried <ramon.fried@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/7] *** Qualcomm Snapdraon serial fixes***
Date: Sat, 12 May 2018 13:15:51 +0300 [thread overview]
Message-ID: <20180512101558.24375-1-ramon.fried@gmail.com> (raw)
In my ongoing effort to get rid of LK (Qualcomm's bootloader) that runs
before U-boot, I found that there were some problems with the uart driver of
Snapdragon.
It appears that the uart only worked because the initialization was previously
done by LK.
While fixing, I also introduced a new pinctrl driver for snapdragon (currently
only enabled for APQ8016).
the pinctrl driver is used for muxing the uart pins and configure the pins IO
properties.
Ramon Fried (7):
db820c: set clk node to be probed before relocation
serial: serial_msm: fail probe if settings clocks fails
serial: serial_msm: initialize uart only before relocation
mach-snapdragon: Fix UART clock flow
mach-snapdragon: Introduce pinctrl driver
db410: added pinctrl node and serial bindings
serial: serial_msm: added pinmux & config
arch/arm/dts/dragonboard410c.dts | 14 ++
arch/arm/dts/dragonboard820c-uboot.dtsi | 14 ++
arch/arm/mach-snapdragon/Makefile | 2 +
arch/arm/mach-snapdragon/clock-apq8016.c | 23 ++-
arch/arm/mach-snapdragon/clock-apq8096.c | 4 +-
arch/arm/mach-snapdragon/clock-snapdragon.c | 17 ++-
arch/arm/mach-snapdragon/clock-snapdragon.h | 9 +-
.../mach-snapdragon/include/mach/sysmap-apq8016.h | 1 +
arch/arm/mach-snapdragon/pinctrl-apq8016.c | 162 +++++++++++++++++++++
arch/arm/mach-snapdragon/pinctrl-snapdragon.c | 118 +++++++++++++++
arch/arm/mach-snapdragon/pinctrl-snapdragon.h | 21 +++
configs/dragonboard410c_defconfig | 5 +
drivers/serial/serial_msm.c | 30 +++-
include/dt-bindings/pinctrl/pinctrl-snapdragon.h | 22 +++
14 files changed, 423 insertions(+), 19 deletions(-)
create mode 100644 arch/arm/mach-snapdragon/pinctrl-apq8016.c
create mode 100644 arch/arm/mach-snapdragon/pinctrl-snapdragon.c
create mode 100644 arch/arm/mach-snapdragon/pinctrl-snapdragon.h
create mode 100644 include/dt-bindings/pinctrl/pinctrl-snapdragon.h
--
2.14.1
next reply other threads:[~2018-05-12 10:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 10:15 Ramon Fried [this message]
2018-05-12 10:15 ` [U-Boot] [PATCH 1/7] db820c: set clk node to be probed before relocation Ramon Fried
2018-05-13 22:00 ` Simon Glass
2018-05-14 7:06 ` Ramon Fried
2018-05-12 10:15 ` [U-Boot] [PATCH 2/7] serial: serial_msm: fail probe if settings clocks fails Ramon Fried
2018-05-13 22:00 ` Simon Glass
2018-05-14 7:07 ` Ramon Fried
2018-05-12 10:15 ` [U-Boot] [PATCH 3/7] serial: serial_msm: initialize uart only before relocation Ramon Fried
2018-05-13 22:00 ` Simon Glass
2018-05-12 10:15 ` [U-Boot] [PATCH 4/7] mach-snapdragon: Fix UART clock flow Ramon Fried
2018-05-12 10:15 ` [U-Boot] [PATCH 5/7] mach-snapdragon: Introduce pinctrl driver Ramon Fried
2018-05-13 22:00 ` Simon Glass
2018-05-14 7:10 ` Ramon Fried
2018-05-14 19:51 ` Simon Glass
2018-05-14 21:23 ` Ramon Fried
2018-05-15 16:02 ` Simon Glass
2018-05-15 16:09 ` Ramon Fried
2018-05-15 16:15 ` Simon Glass
2018-05-16 5:37 ` Ramon Fried
2018-05-12 10:15 ` [U-Boot] [PATCH 6/7] db410: added pinctrl node and serial bindings Ramon Fried
2018-05-13 22:00 ` Simon Glass
2018-05-12 10:15 ` [U-Boot] [PATCH 7/7] serial: serial_msm: added pinmux & config Ramon Fried
2018-05-13 22:00 ` Simon Glass
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=20180512101558.24375-1-ramon.fried@gmail.com \
--to=ramon.fried@gmail.com \
--cc=u-boot@lists.denx.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