From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Doug Anderson <dianders@chromium.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: max77686: fix support for devices without irq specified
Date: Fri, 08 Aug 2014 12:58:50 +0200 [thread overview]
Message-ID: <53E4AD6A.4000705@collabora.co.uk> (raw)
In-Reply-To: <1407495251.28710.2.camel@AMDC1943>
Hello Krzysztof,
On 08/08/2014 12:54 PM, Krzysztof Kozlowski wrote:
>> >>
>> >> Not sufficient. You have to also fix RTC driver (OOPS from Trats2
>> >> attached). Also consider adding checks for (max77686->irq) to the
>> >> suspend and resume.
>> >>
>> >
>> > Right, the max77686 RTC driver assumes that an IRQ domain will be created on the
>> > mfd driver so a virtual IRQ can be mapped for the RTC alarm1 IRQ. This
>> > assumptions comes from the fact that the "interrupt" property is required
>> > according to the DT binding doc.
>> >
>>
>> Although for Trats2 I see that arch/arm/boot/dts/exynos4412-trats2.dts defines
>> an interrupt, so I wonder why regmap_irq_get_virq() is giving an oops there:
>>
>> max77686_pmic@09 {
>> compatible = "maxim,max77686";
>> interrupt-parent = <&gpx0>;
>> interrupts = <7 0>;
>> reg = <0x09>;
>> #clock-cells = <1>;
>> ...
>
> Because I am a nasty user :) and I removed the interrupts properties
> manually (to test how the RTC will behave). Still the driver shouldn't
> oops.
>
Oh, now it makes sense :)
Yes, I agree with you that the driver should not oops. The probe should fail
though if no IRQ domain was created on the MFD driver since that DT property is
required.
I'll send a fix for this today, thanks a lot for reporting it.
>>
>>
>> > So the max77686 RTC wakealarm was not working for these boards before?
>
> I don't know for Odroid but on Trats2 it works fine.
>
>> >
>> > Just to be sure that I understand the issue: these boards don't really have an
>> > IRQ connected to the PMIC, is not that this information is just missing in the
>> > Device Tree, right?
>> >
>>
>> By looking at Odroid's 3.8 based vendor tree I see that an IRQ for the max77686
>> PMIC is defined [0] using platform data:
>>
>> static struct max77686_platform_data exynos4_max77686_info = {
>> .irq_gpio = EXYNOS4_GPX3(2),
>> .ono = EXYNOS4_GPX1(2),
>> .num_regulators = ARRAY_SIZE(max77686_regulators),
>> .regulators = max77686_regulators,
>> ...
>>
>> So maybe this information is missing in
>> arch/arm/boot/dts/exynos4412-odroid-common.dtsi?
>
> Yes, it seems it is missing.
>
Indeed.
> Best regards,
> Krzysztof
>
Best regards,
Javier
next prev parent reply other threads:[~2014-08-08 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 16:09 [PATCH] mfd: max77686: fix support for devices without irq specified Bartlomiej Zolnierkiewicz
2014-08-08 7:59 ` Krzysztof Kozlowski
2014-08-08 8:58 ` Javier Martinez Canillas
2014-08-08 10:09 ` Javier Martinez Canillas
2014-08-08 10:54 ` Krzysztof Kozlowski
2014-08-08 10:58 ` Javier Martinez Canillas [this message]
2014-08-08 12:24 ` Bartlomiej Zolnierkiewicz
2014-08-08 12:38 ` 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=53E4AD6A.4000705@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox