From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org, Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] WIP: gnss: merge MTK driver into UBX driver
Date: Mon, 12 Jun 2023 13:35:26 +0200 [thread overview]
Message-ID: <ZIcC/sg59Ti+lL1N@ninjato> (raw)
In-Reply-To: <20230523064310.3005-2-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 3154 bytes --]
On Tue, May 23, 2023 at 08:43:06AM +0200, Wolfram Sang wrote:
> This is a proof-of-concept how easy it is to merge those two drivers as
> they are extremly similar. The differences can be abstracted away
> easily. Further work (renaming from 'ubx' to something more generic,
> removing the MTK driver, ...) is postponed until there is agrement that
> merging these drivers is actually wanted. I vote for it, though. I have
> updates to the UBX driver which do make sense for the MTK driver as
> well. Code saving is also a plus. We can always fork into a specific
> driver again if we'd ever need that.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Johan, just from a gut feeling or a hi level glimpse: is this merging of
the driver worth pursuing?
Thanks and all the best,
Wolfram
> ---
> drivers/gnss/ubx.c | 30 +++++++++++++++++++++++++-----
> 1 file changed, 25 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gnss/ubx.c b/drivers/gnss/ubx.c
> index c951be202ca2..c01e1e875727 100644
> --- a/drivers/gnss/ubx.c
> +++ b/drivers/gnss/ubx.c
> @@ -63,12 +63,31 @@ static const struct gnss_serial_ops ubx_gserial_ops = {
> .set_power = ubx_set_power,
> };
>
> +struct ubx_info {
> + enum gnss_type type;
> + char *v_bckp_name;
> +};
> +
> +const struct ubx_info ubx_info_ubx = {
> + .type = GNSS_TYPE_UBX,
> + .v_bckp_name = "v-bckp",
> +};
> +
> +const struct ubx_info ubx_info_mtk = {
> + .type = GNSS_TYPE_MTK,
> + .v_bckp_name = "vbackup",
> +};
> +
> static int ubx_probe(struct serdev_device *serdev)
> {
> + const struct ubx_info *info = of_device_get_match_data(&serdev->dev);
> struct gnss_serial *gserial;
> struct ubx_data *data;
> int ret;
>
> + if (!info)
> + return -ENOENT;
> +
> gserial = gnss_serial_allocate(serdev, sizeof(*data));
> if (IS_ERR(gserial)) {
> ret = PTR_ERR(gserial);
> @@ -77,7 +96,7 @@ static int ubx_probe(struct serdev_device *serdev)
>
> gserial->ops = &ubx_gserial_ops;
>
> - gserial->gdev->type = GNSS_TYPE_UBX;
> + gserial->gdev->type = info->type;
>
> data = gnss_serial_get_drvdata(gserial);
>
> @@ -87,7 +106,7 @@ static int ubx_probe(struct serdev_device *serdev)
> goto err_free_gserial;
> }
>
> - data->v_bckp = devm_regulator_get_optional(&serdev->dev, "v-bckp");
> + data->v_bckp = devm_regulator_get_optional(&serdev->dev, info->v_bckp_name);
> if (IS_ERR(data->v_bckp)) {
> ret = PTR_ERR(data->v_bckp);
> if (ret == -ENODEV)
> @@ -130,9 +149,10 @@ static void ubx_remove(struct serdev_device *serdev)
>
> #ifdef CONFIG_OF
> static const struct of_device_id ubx_of_match[] = {
> - { .compatible = "u-blox,neo-6m" },
> - { .compatible = "u-blox,neo-8" },
> - { .compatible = "u-blox,neo-m8" },
> + { .compatible = "u-blox,neo-6m", .data = &ubx_info_ubx, },
> + { .compatible = "u-blox,neo-8", .data = &ubx_info_ubx, },
> + { .compatible = "u-blox,neo-m8", .data = &ubx_info_ubx, },
> + { .compatible = "globaltop,pa6h", .data = &ubx_info_mtk },
> {},
> };
> MODULE_DEVICE_TABLE(of, ubx_of_match);
> --
> 2.35.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-12 11:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:43 [RFC PATCH 0/5] gnss: updates to support the Renesas KingFisher board Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 1/5] WIP: gnss: merge MTK driver into UBX driver Wolfram Sang
2023-06-12 11:35 ` Wolfram Sang [this message]
2023-06-20 7:13 ` Johan Hovold
2023-06-20 9:00 ` Wolfram Sang
2023-06-20 10:21 ` Wolfram Sang
2023-06-20 14:50 ` Johan Hovold
2023-05-23 6:43 ` [RFC PATCH 2/5] gnss: ubx: use new helper to remove open coded regulator handling Wolfram Sang
2023-06-20 8:48 ` Johan Hovold
2023-06-20 9:04 ` Wolfram Sang
2023-06-20 9:08 ` Johan Hovold
2023-05-23 6:43 ` [RFC PATCH 3/5] gnss: ubx: 'vcc' can be optional Wolfram Sang
2023-06-20 7:15 ` Johan Hovold
2023-06-20 9:04 ` Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 4/5] gnss: ubx: add support for the reset gpio Wolfram Sang
2023-06-20 7:17 ` Johan Hovold
2023-06-20 9:06 ` Wolfram Sang
2023-06-20 9:12 ` Johan Hovold
2023-06-20 9:41 ` Wolfram Sang
2023-06-20 10:05 ` Johan Hovold
2023-06-20 10:14 ` Wolfram Sang
2023-05-23 6:43 ` [RFC PATCH 5/5] arm64: dts: renesas: ulcb-kf: add node for GPS Wolfram Sang
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=ZIcC/sg59Ti+lL1N@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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