From: alison@she-devel.com
To: johan@kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, alison@she-devel.com,
achaiken@aurora.tech, kernel test robot <lkp@intel.com>
Subject: [PATCH v5 0/2] support config of U-Blox Zed-F9P GNSS
Date: Sun, 7 May 2023 18:11:57 -0700 [thread overview]
Message-ID: <20230508011159.263322-1-alison@she-devel.com> (raw)
From: Alison Chaiken <alison@she-devel.com>
Add generalized support for setting arbitrary configuration of the
U-Blox Zed-F9P GNSS. Employ the new functionality to set the baud rate
of the Zed-F9P if the devicetree specifies a non-default value.
Tested with 6.1.22, only on a U-Blox Zed-F9P GNSS.
V5 -> V4 Wrap all new code in a CONFIG_OF=y check and fixes
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202305070938.8vWQFfIQ-lkp@intel.com/
V4 -> V3 Lookup device-specific properties by matching driver data.
V2 -> V3 Add email recipients whom I foolishly missed the first two times.
V1 -> V2 Fixes error identified by kernel test robot:
Alison Chaiken (2):
gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud
dt-bindings: gnss: Add U-Blox Zed-F9
.../bindings/gnss/u-blox,neo-6m.yaml | 1 +
drivers/gnss/ubx.c | 242 +++++++++++++++++-
2 files changed, 232 insertions(+), 11 deletions(-)
base-commit: ac9a78681b921877518763ba0e89202254349d1b
--
2.39.2
next reply other threads:[~2023-05-08 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 1:11 alison [this message]
2023-05-08 1:11 ` [PATCH v4 1/2] gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud alison
2023-05-08 7:52 ` kernel test robot
2023-05-08 8:00 ` Krzysztof Kozlowski
2023-05-08 1:11 ` [PATCH 2/2] dt-bindings: gnss: Add U-Blox Zed-F9 alison
2023-05-08 2:26 ` Rob Herring
2023-05-08 6:39 ` Krzysztof Kozlowski
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=20230508011159.263322-1-alison@she-devel.com \
--to=alison@she-devel.com \
--cc=achaiken@aurora.tech \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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).