From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: alison@she-devel.com, 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, achaiken@aurora.tech
Subject: Re: [PATCH v4 1/2] gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud
Date: Mon, 8 May 2023 10:00:53 +0200 [thread overview]
Message-ID: <dda6eef1-ecce-a98e-605f-b9640827c6fd@linaro.org> (raw)
In-Reply-To: <20230508011159.263322-2-alison@she-devel.com>
On 08/05/2023 03:11, alison@she-devel.com wrote:
> From: Alison Chaiken <achaiken@aurora.tech>
>
> Add support for setting the baud rate of U-Blox Zed-F9P GNSS devices.
> Provide functions that support writing of arbitrary configuration
> messages to the device plus one that specifically configures the baud
> rate. Override the default gnss_serial_open() with a new method that
> writes the configuration message to the GNSS if the devicetree declares
> it to be a Zed F9P and requests a non-default baud. Add a boolean flag
> to the ubx_data private data of the GNSS driver in order to track
> whether the configuration message has already been written. Set the Zed
> F9P to its default port speed if the devicetree does not specify a
> value.
>
> Signed-off-by: Alison Chaiken <achaiken@aurora.tech>
> ---
>
> V5 -> V4 Compile out the changes if CONFIG_OF is not set.
Judging by the number of kernel test robot failures, I am not sure if
you tested the patch.
Anyway, don't add more #ifdefs, that's not a correct approach. Depending
on the case, you either remove if entirely or add __maybe_unused. Why
did you need to add the #ifdefs?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-08 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 1:11 [PATCH v5 0/2] support config of U-Blox Zed-F9P GNSS alison
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 [this message]
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=dda6eef1-ecce-a98e-605f-b9640827c6fd@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=achaiken@aurora.tech \
--cc=alison@she-devel.com \
--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=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).