From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Lee Jones <lee@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Andre Przywara <andre.przywara@arm.com>
Cc: linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Shengyu Qu <wiagn233@outlook.com>,
Martin Botka <martin.botka1@gmail.com>,
Matthew Croughan <matthew.croughan@nix.how>
Subject: Re: [PATCH v2] mfd: axp20x: Generalise handling without interrupt
Date: Tue, 05 Sep 2023 22:28:10 +0200 [thread overview]
Message-ID: <22003475.EfDdHjke4D@archlinux> (raw)
In-Reply-To: <20230828213229.20332-1-andre.przywara@arm.com>
On Monday, August 28, 2023 11:32:29 PM CEST Andre Przywara wrote:
> At the moment we allow the AXP15060 and the AXP806 PMICs to omit the
> interrupt line to the SoC, and we skip registering the PEK (power key)
> driver in this case, since that crashes when no IRQ is described in the
> DT node.
> The IRQ pin potentially not being connected to anything does affect more
> PMICs, though, and the PEK driver is not the only one requiring an
> interrupt: at least the AC power supply driver crashes in a similar
> fashion.
>
> Generalise the handling of AXP MFD devices when the platform tables
> describe no interrupt, by allowing each device to specify an alternative
> MFD list for this case. If no specific alternative is specified, we go
> with the safe default of "just the regulators", which matches the current
> situation.
>
> This enables new devices using the AXP313a PMIC, but not connecting the
> IRQ pin.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> Changelog v2 .. v1:
> - drop reordering approach, use separate cell lists
>
> drivers/mfd/axp20x.c | 44 ++++++++++++++++++++++++--------------------
> 1 file changed, 24 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
> index c03bc5cda080a..239e7f18956ae 100644
> --- a/drivers/mfd/axp20x.c
> +++ b/drivers/mfd/axp20x.c
> @@ -1133,6 +1133,8 @@ int axp20x_match_device(struct axp20x_dev *axp20x)
> struct device *dev = axp20x->dev;
> const struct acpi_device_id *acpi_id;
> const struct of_device_id *of_id;
> + const struct mfd_cell *cells_no_irq = NULL;
> + int nr_cells_no_irq = 0;
>
> if (dev->of_node) {
> of_id = of_match_device(dev->driver->of_match_table,
dev);
> @@ -1207,14 +1209,15 @@ int axp20x_match_device(struct axp20x_dev *axp20x)
> * if there is no interrupt line.
> */
> if (of_property_read_bool(axp20x->dev->of_node,
> - "x-powers,self-
working-mode") &&
> - axp20x->irq > 0) {
> + "x-powers,self-
working-mode")) {
> axp20x->nr_cells =
ARRAY_SIZE(axp806_self_working_cells);
> axp20x->cells = axp806_self_working_cells;
> } else {
> axp20x->nr_cells = ARRAY_SIZE(axp806_cells);
> axp20x->cells = axp806_cells;
> }
> + nr_cells_no_irq = ARRAY_SIZE(axp806_cells);
> + cells_no_irq = axp806_cells;
> axp20x->regmap_cfg = &axp806_regmap_config;
> axp20x->regmap_irq_chip = &axp806_regmap_irq_chip;
> break;
> @@ -1238,24 +1241,8 @@ int axp20x_match_device(struct axp20x_dev *axp20x)
> axp20x->regmap_irq_chip = &axp803_regmap_irq_chip;
> break;
> case AXP15060_ID:
> - /*
> - * Don't register the power key part if there is no
interrupt
> - * line.
> - *
> - * Since most use cases of AXP PMICs are Allwinner
SOCs, board
> - * designers follow Allwinner's reference design and
connects
> - * IRQ line to SOC, there's no need for those variants
to deal
> - * with cases that IRQ isn't connected. However,
AXP15660 is
> - * used by some other vendors' SOCs that didn't connect
IRQ
> - * line, we need to deal with this case.
> - */
> - if (axp20x->irq > 0) {
> - axp20x->nr_cells =
ARRAY_SIZE(axp15060_cells);
> - axp20x->cells = axp15060_cells;
> - } else {
> - axp20x->nr_cells =
ARRAY_SIZE(axp_regulator_only_cells);
> - axp20x->cells = axp_regulator_only_cells;
> - }
> + axp20x->nr_cells = ARRAY_SIZE(axp15060_cells);
> + axp20x->cells = axp15060_cells;
> axp20x->regmap_cfg = &axp15060_regmap_config;
> axp20x->regmap_irq_chip = &axp15060_regmap_irq_chip;
> break;
> @@ -1263,6 +1250,23 @@ int axp20x_match_device(struct axp20x_dev *axp20x)
> dev_err(dev, "unsupported AXP20X ID %lu\n", axp20x-
>variant);
> return -EINVAL;
> }
> +
> + /*
> + * Use an alternative cell array when no interrupt line is
connected,
> + * since IRQs are required by some drivers.
> + * The default is the safe "regulator-only", as this works fine
without
> + * an interrupt specified.
> + */
> + if (axp20x->irq <= 0) {
> + if (cells_no_irq) {
> + axp20x->nr_cells = nr_cells_no_irq;
> + axp20x->cells = cells_no_irq;
> + } else {
> + axp20x->nr_cells =
ARRAY_SIZE(axp_regulator_only_cells);
> + axp20x->cells = axp_regulator_only_cells;
axp806_cells (old value for AXP806_ID without irq) and
axp_regulator_only_cells differs in id field. Is that an issue?
Best regards,
Jernej
> + }
> + }
> +
> dev_info(dev, "AXP20x variant %s found\n",
> axp20x_model_names[axp20x->variant]);
next prev parent reply other threads:[~2023-09-05 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 21:32 [PATCH v2] mfd: axp20x: Generalise handling without interrupt Andre Przywara
2023-09-05 20:28 ` Jernej Škrabec [this message]
2023-09-05 20:46 ` Andre Przywara
2023-09-05 21:03 ` Jernej Škrabec
2023-09-20 10:17 ` (subset) " Lee Jones
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=22003475.EfDdHjke4D@archlinux \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=martin.botka1@gmail.com \
--cc=matthew.croughan@nix.how \
--cc=wens@csie.org \
--cc=wiagn233@outlook.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.