From: Mark Brown <broonie@kernel.org> To: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Cc: Lee Jones <lee.jones@linaro.org>, Samuel Ortiz <sameo@linux.intel.com>, Mike Turquette <mturquette@linaro.org>, Liam Girdwood <lgirdwood@gmail.com>, Alessandro Zummo <a.zummo@towertech.it>, Kukjin Kim <kgene.kim@samsung.com>, Doug Anderson <dianders@chromium.org>, Olof Johansson <olof@lixom.net>, Sjoerd Simons <sjoerd.simons@collabora.co.uk>, Daniel Stone <daniels@collabora.com>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/5] mfd: Add driver for Maxim 77802 Power Management IC Date: Mon, 9 Jun 2014 20:47:13 +0100 [thread overview] Message-ID: <20140609194713.GF5099@sirena.org.uk> (raw) In-Reply-To: <1402306670-17041-2-git-send-email-javier.martinez@collabora.co.uk> [-- Attachment #1: Type: text/plain, Size: 1755 bytes --] On Mon, Jun 09, 2014 at 11:37:46AM +0200, Javier Martinez Canillas wrote: > +Optional node: > +- voltage-regulators : The regulators of max77802 have to be instantiated > + under subnode named "voltage-regulators" using the following format. Every other PMIC calls this node regulators... > + regulator_name { > + regulator-compatible = LDOn/BUCKn regulator-compatible is deprecated, use the node name instead. > +config MFD_MAX77802 > + bool "Maxim Integrated MAX77802 PMIC Support" Why is this bool and not tristate? > +int max77802_irq_resume(struct max77802_dev *max77802) > +{ > + /* > + * The IRQ that woke us up may still need to be ACK'ed on resume. > + * If it isn't ever ACK'ed, future IRQs may not be delivered. > + */ > + if (max77802->irq) > + max77802_irq_thread(0, max77802); > + > + return 0; > +} As covered in another subthread all this code looks like it should be regmap-irq. > + if (regmap_read(max77802->regmap, > + MAX77802_REG_DEVICE_ID, &data) < 0) { > + dev_err(max77802->dev, > + "device not found on this channel (this is not an error)\n"); > + return -ENODEV; If this is not an error why is it printed as dev_err()? It does look like an error to me, though. > + } else { > + dev_info(max77802->dev, "device found\n"); > + } These sort of prints are just noise, remove this unless there is some revision information you can display. It's also better practice to check that the device ID is actually what was expected in case there was an error in the DT. > +static const struct i2c_device_id max77802_i2c_id[] = { > + { "max77802", TYPE_MAX77802 }, > + { } > +}; > +MODULE_DEVICE_TABLE(i2c, max77802_i2c_id); We have type information here but not in the OF ID table (not that we ever look at it). [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/5] mfd: Add driver for Maxim 77802 Power Management IC Date: Mon, 9 Jun 2014 20:47:13 +0100 [thread overview] Message-ID: <20140609194713.GF5099@sirena.org.uk> (raw) In-Reply-To: <1402306670-17041-2-git-send-email-javier.martinez@collabora.co.uk> On Mon, Jun 09, 2014 at 11:37:46AM +0200, Javier Martinez Canillas wrote: > +Optional node: > +- voltage-regulators : The regulators of max77802 have to be instantiated > + under subnode named "voltage-regulators" using the following format. Every other PMIC calls this node regulators... > + regulator_name { > + regulator-compatible = LDOn/BUCKn regulator-compatible is deprecated, use the node name instead. > +config MFD_MAX77802 > + bool "Maxim Integrated MAX77802 PMIC Support" Why is this bool and not tristate? > +int max77802_irq_resume(struct max77802_dev *max77802) > +{ > + /* > + * The IRQ that woke us up may still need to be ACK'ed on resume. > + * If it isn't ever ACK'ed, future IRQs may not be delivered. > + */ > + if (max77802->irq) > + max77802_irq_thread(0, max77802); > + > + return 0; > +} As covered in another subthread all this code looks like it should be regmap-irq. > + if (regmap_read(max77802->regmap, > + MAX77802_REG_DEVICE_ID, &data) < 0) { > + dev_err(max77802->dev, > + "device not found on this channel (this is not an error)\n"); > + return -ENODEV; If this is not an error why is it printed as dev_err()? It does look like an error to me, though. > + } else { > + dev_info(max77802->dev, "device found\n"); > + } These sort of prints are just noise, remove this unless there is some revision information you can display. It's also better practice to check that the device ID is actually what was expected in case there was an error in the DT. > +static const struct i2c_device_id max77802_i2c_id[] = { > + { "max77802", TYPE_MAX77802 }, > + { } > +}; > +MODULE_DEVICE_TABLE(i2c, max77802_i2c_id); We have type information here but not in the OF ID table (not that we ever look at it). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140609/4eb88b9b/attachment-0001.sig>
next prev parent reply other threads:[~2014-06-09 19:47 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-09 9:37 [PATCH 0/5] Add Maxim 77802 PMIC support Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 9:37 ` [PATCH 1/5] mfd: Add driver for Maxim 77802 Power Management IC Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 10:22 ` Krzysztof Kozlowski 2014-06-09 10:22 ` Krzysztof Kozlowski 2014-06-09 11:56 ` Mark Brown 2014-06-09 11:56 ` Mark Brown 2014-06-09 23:07 ` Javier Martinez Canillas 2014-06-09 23:07 ` Javier Martinez Canillas 2014-06-09 19:47 ` Mark Brown [this message] 2014-06-09 19:47 ` Mark Brown 2014-06-09 23:40 ` Javier Martinez Canillas 2014-06-09 23:40 ` Javier Martinez Canillas 2014-06-09 9:37 ` [PATCH 2/5] regulator: Add driver for Maxim 77802 PMIC regulators Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 19:38 ` Mark Brown 2014-06-09 19:38 ` Mark Brown 2014-06-09 19:38 ` Mark Brown 2014-06-09 23:29 ` Javier Martinez Canillas 2014-06-09 23:29 ` Javier Martinez Canillas 2014-06-10 10:53 ` Mark Brown 2014-06-10 10:53 ` Mark Brown 2014-06-09 9:37 ` [PATCH 3/5] clk: Add driver for Maxim 77802 PMIC clocks Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-16 8:44 ` Lee Jones 2014-06-16 8:44 ` Lee Jones 2014-06-16 8:54 ` Javier Martinez Canillas 2014-06-16 8:54 ` Javier Martinez Canillas 2014-06-09 9:37 ` [PATCH 4/5] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 9:37 ` [PATCH 5/5] ARM: dts: Add max77802 device node for exynos5420-peach-pit Javier Martinez Canillas 2014-06-09 9:37 ` Javier Martinez Canillas 2014-06-09 10:16 ` [PATCH 0/5] Add Maxim 77802 PMIC support Krzysztof Kozlowski 2014-06-09 10:16 ` Krzysztof Kozlowski 2014-06-09 16:04 ` Doug Anderson 2014-06-09 16:04 ` Doug Anderson 2014-06-09 16:04 ` Doug Anderson 2014-06-09 22:55 ` Javier Martinez Canillas 2014-06-09 22:55 ` Javier Martinez Canillas 2014-06-09 22:55 ` Javier Martinez Canillas 2014-06-09 23:57 ` Doug Anderson 2014-06-09 23:57 ` Doug Anderson 2014-06-09 23:57 ` Doug Anderson 2014-06-10 7:45 ` Krzysztof Kozlowski 2014-06-10 7:45 ` Krzysztof Kozlowski 2014-06-10 7:45 ` Krzysztof Kozlowski 2014-06-10 7:32 ` Krzysztof Kozlowski 2014-06-10 7:32 ` Krzysztof Kozlowski 2014-06-10 7:32 ` Krzysztof Kozlowski 2014-06-10 7:50 ` Javier Martinez Canillas 2014-06-10 7:50 ` Javier Martinez Canillas 2014-06-10 7:50 ` Javier Martinez Canillas
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=20140609194713.GF5099@sirena.org.uk \ --to=broonie@kernel.org \ --cc=a.zummo@towertech.it \ --cc=daniels@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=javier.martinez@collabora.co.uk \ --cc=kgene.kim@samsung.com \ --cc=lee.jones@linaro.org \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mturquette@linaro.org \ --cc=olof@lixom.net \ --cc=sameo@linux.intel.com \ --cc=sjoerd.simons@collabora.co.uk \ --cc=tomeu.vizoso@collabora.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: linkBe 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.