From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@analog.com>,
lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, sre@kernel.org,
lgirdwood@gmail.com, broonie@kernel.org
Cc: Nurettin.Bolucu@analog.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/6] drivers: power: supply: add MAX77659 charger support
Date: Tue, 20 Dec 2022 15:51:16 +0100 [thread overview]
Message-ID: <9915e079-c6b5-a8f4-734e-f0325809efd0@linaro.org> (raw)
In-Reply-To: <20221220132250.19383-4-Zeynep.Arslanbenzer@analog.com>
On 20/12/2022 14:22, Zeynep Arslanbenzer wrote:
> This patch adds battery charger driver for MAX77659.
>
> Signed-off-by: Nurettin Bolucu <Nurettin.Bolucu@analog.com>
> Signed-off-by: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@analog.com>
> ---
> MAINTAINERS | 1 +
> drivers/power/supply/Kconfig | 7 +
> drivers/power/supply/Makefile | 1 +
> drivers/power/supply/max77659-charger.c | 547 ++++++++++++++++++++++++
> 4 files changed, 556 insertions(+)
> create mode 100644 drivers/power/supply/max77659-charger.c
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e7a9cadf0ff2..b3e307163063 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12647,6 +12647,7 @@ L: linux-kernel@vger.kernel.org
> S: Maintained
> F: Documentation/devicetree/bindings/mfd/adi,max77659.yaml
> F: drivers/mfd/max77659.c
> +F: drivers/power/supply/max77659-charger.c
> F: include/linux/mfd/max77659.h
>
> MAXIM MAX77714 PMIC MFD DRIVER
> diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig
> index 0bbfe6a7ce4d..d38ef40ae9ee 100644
> --- a/drivers/power/supply/Kconfig
> +++ b/drivers/power/supply/Kconfig
> @@ -565,6 +565,13 @@ config CHARGER_MAX77650
> Say Y to enable support for the battery charger control of MAX77650
> PMICs.
>
> +config CHARGER_MAX77659
> + tristate "Analog Devices MAX77659 battery charger driver"
> + depends on MFD_MAX77659
> + help
> + Say Y to enable support for the battery charger control of MAX77659
> + PMICs.
> +
> config CHARGER_MAX77693
> tristate "Maxim MAX77693 battery charger driver"
> depends on MFD_MAX77693
> diff --git a/drivers/power/supply/Makefile b/drivers/power/supply/Makefile
> index 0ee8653e882e..e8646896bcd2 100644
> --- a/drivers/power/supply/Makefile
> +++ b/drivers/power/supply/Makefile
> @@ -76,6 +76,7 @@ obj-$(CONFIG_CHARGER_LTC4162L) += ltc4162-l-charger.o
> obj-$(CONFIG_CHARGER_MAX14577) += max14577_charger.o
> obj-$(CONFIG_CHARGER_DETECTOR_MAX14656) += max14656_charger_detector.o
> obj-$(CONFIG_CHARGER_MAX77650) += max77650-charger.o
> +obj-$(CONFIG_CHARGER_MAX77659) += max77659-charger.o
> obj-$(CONFIG_CHARGER_MAX77693) += max77693_charger.o
> obj-$(CONFIG_CHARGER_MAX77976) += max77976_charger.o
> obj-$(CONFIG_CHARGER_MAX8997) += max8997_charger.o
> diff --git a/drivers/power/supply/max77659-charger.c b/drivers/power/supply/max77659-charger.c
> new file mode 100644
> index 000000000000..dfdbd484f7cd
> --- /dev/null
> +++ b/drivers/power/supply/max77659-charger.c
> @@ -0,0 +1,547 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +
> +#include <linux/bitfield.h>
> +#include <linux/interrupt.h>
> +#include <linux/mfd/max77659.h>
> +#include <linux/module.h>
> +#include <linux/mutex.h>
> +#include <linux/of_irq.h>
> +#include <linux/platform_device.h>
> +#include <linux/power_supply.h>
> +#include <linux/regmap.h>
> +
> +#define MAX77659_IRQ_WORK_DELAY 0
> +#define MAX77659_CHARGER_CURRENT_MAX 300000
> +#define MAX77659_CHARGER_CURRENT_MIN 7500
> +#define MAX77659_CHARGER_CURRENT_STEP 7500
> +#define MAX77659_CHARGER_TOPOFF_TIMER_STEP 5
> +
> +#define MAX77659_REG_STAT_CHG_A 0x02
Same problems as your other patch - unreadable code. Two different
coding styles...
> +#define MAX77659_REG_STAT_CHG_B 0x03
> +#define MAX77659_REG_CNFG_CHG_A 0x20
> +#define MAX77659_REG_CNFG_CHG_B 0x21
> +#define MAX77659_REG_CNFG_CHG_C 0x22
> +#define MAX77659_REG_CNFG_CHG_D 0x23
> +#define MAX77659_REG_CNFG_CHG_E 0x24
> +#define MAX77659_REG_CNFG_CHG_F 0x25
> +#define MAX77659_REG_CNFG_CHG_G 0x26
> +#define MAX77659_REG_CNFG_CHG_H 0x27
> +#define MAX77659_REG_CNFG_CHG_I 0x28
> +
> +#define MAX77659_BIT_STAT_A_VSYSY_MIN_STAT BIT(4)
> +#define MAX77659_BIT_STAT_A_TJ_REG_STAT BIT(3)
> +#define MAX77659_BIT_STAT_A_THM_DTLS GENMASK(2, 0)
> +#define MAX77659_BIT_STAT_B_CHG_DTLS GENMASK(7, 4)
> +#define MAX77659_BIT_STAT_B_CHGIN_DTSL GENMASK(3, 2)
> +#define MAX77659_BIT_STAT_B_CHG BIT(1)
> +#define MAX77659_BIT_CNFG_B_CHG_EN BIT(0)
> +#define MAX77659_BIT_CNFG_C_TOPOFFTIMER GENMASK(2, 0)
> +#define MAX77659_BIT_CNFG_E_CC GENMASK(7, 2)
> +#define MAX77659_BIT_CNFG_E_TFASTCHG GENMASK(1, 0)
> +#define MAX77659_BIT_CNFG_G_CHG_CV GENMASK(7, 2)
> +
(...)
> +
> + charger->psy_chg_d.name = MAX77659_CHARGER_NAME;
> + charger->psy_chg_d.type = POWER_SUPPLY_TYPE_UNKNOWN;
> + charger->psy_chg_d.get_property = max77659_charger_get_property;
> + charger->psy_chg_d.set_property = max77659_charger_set_property;
> + charger->psy_chg_d.properties = max77659_charger_props;
> + charger->psy_chg_d.property_is_writeable = max77659_property_is_writeable;
> + charger->psy_chg_d.num_properties = ARRAY_SIZE(max77659_charger_props);
> + charger_cfg.drv_data = charger;
> + charger_cfg.supplied_to = chg_supplied_to;
> + charger_cfg.of_node = dev->of_node;
> + charger_cfg.num_supplicants = ARRAY_SIZE(chg_supplied_to);
> +
> + ret = max77659_charger_initialize(charger);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to initialize charger\n");
> +
> + for (i = 0; i < MAX77659_CHG_IRQ_MAX; i++) {
> + charger->irq_arr[i] = regmap_irq_get_virq(max77659->irqc_chg, i);
> +
> + if (charger->irq_arr[i] < 0)
> + return dev_err_probe(dev, -EINVAL,
> + "Invalid IRQ for MAX77659_CHG_IRQ %d\n", i);
> +
> + ret = devm_request_threaded_irq(dev, charger->irq_arr[i],
> + NULL, max77659_charger_isr, IRQF_TRIGGER_FALLING,
This does not look like wrapped to Linux coding style (which is
explicitly set at 80).
> + max77659_irq_descs[i], charger);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to request irq: %d\n",
> + charger->irq_arr[i]);
> + }
> +
> + charger->psy_chg = devm_power_supply_register(dev, &charger->psy_chg_d, &charger_cfg);
> + if (IS_ERR(charger->psy_chg))
> + return dev_err_probe(dev, PTR_ERR(charger->psy_chg),
> + "Failed to register power supply\n");
> +
> + return 0;
> +}
> +
> +static const struct of_device_id max77659_charger_of_id[] = {
> + { .compatible = "adi,max77659-charger" },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, max77659_charger_of_id);
> +
> +static const struct platform_device_id max77659_charger_id[] = {
> + { MAX77659_CHARGER_NAME, 0, },
Same comment.
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(platform, max77659_charger_id);
> +
> +static struct platform_driver max77659_charger_driver = {
> + .driver = {
> + .name = MAX77659_CHARGER_NAME,
> + .of_match_table = of_match_ptr(max77659_charger_of_id),
Same problem.
> + },
> + .probe = max77659_charger_probe,
> + .id_table = max77659_charger_id,
> +};
> +
> +module_platform_driver(max77659_charger_driver);
> +
> +MODULE_DESCRIPTION("MAX77659 Charger Driver");
> +MODULE_AUTHOR("Nurettin.Bolucu@analog.com, Zeynep.Arslanbenzer@analog.com");
> +MODULE_LICENSE("GPL");
> +MODULE_VERSION("1.0");
Drop version. From all possible places.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-20 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 13:22 [PATCH 0/6] drivers: mfd: Add MAX77659 MFD and related device drivers Zeynep Arslanbenzer
2022-12-20 13:22 ` [PATCH 1/6] drivers: mfd: add MAX77659 PMIC support Zeynep Arslanbenzer
2022-12-20 14:47 ` Krzysztof Kozlowski
2022-12-20 13:22 ` [PATCH 2/6] dt-bindings: mfd: add MAX77659 binding Zeynep Arslanbenzer
2022-12-20 14:43 ` Krzysztof Kozlowski
2022-12-20 16:40 ` Rob Herring
2022-12-20 13:22 ` [PATCH 3/6] drivers: power: supply: add MAX77659 charger support Zeynep Arslanbenzer
2022-12-20 14:51 ` Krzysztof Kozlowski [this message]
2023-01-02 20:44 ` Sebastian Reichel
2022-12-20 13:22 ` [PATCH 4/6] dt-bindings: power: supply: add MAX77659 charger binding Zeynep Arslanbenzer
2022-12-20 14:54 ` Krzysztof Kozlowski
2023-04-17 21:43 ` Arslanbenzer, Zeynep
2023-04-18 7:09 ` Krzysztof Kozlowski
2023-04-18 9:41 ` Arslanbenzer, Zeynep
2023-04-18 12:30 ` Krzysztof Kozlowski
2022-12-20 13:22 ` [PATCH 5/6] drivers: regulator: add MAX77659 regulator support Zeynep Arslanbenzer
2022-12-20 13:22 ` [PATCH 6/6] dt-bindings: regulator: add MAX77659 regulator binding Zeynep Arslanbenzer
2022-12-20 14:55 ` 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=9915e079-c6b5-a8f4-734e-f0325809efd0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Nurettin.Bolucu@analog.com \
--cc=Zeynep.Arslanbenzer@analog.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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).