From: Chanwoo Choi <cw00.choi@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH RESEND 2/3] extcon: max77693: Request only specific interrupts
Date: Wed, 22 Oct 2014 18:04:14 +0900 [thread overview]
Message-ID: <5447730E.80500@samsung.com> (raw)
In-Reply-To: <1413967540-27626-2-git-send-email-k.kozlowski@samsung.com>
Hi Krzysztof,
The extcon-max77693.c was tested by all cables (mhl, hdmi, usb, usb-host, dock for audio play, dock for mhl).
with default_init_data register setting. If you deletes legacy default_init_data[] register setting,
extcon-max77693.c can not guarantee the operation of upper cables.
So, I want to maintain 'default_init_data' register setting value.
Thanks,
Chanwoo Choi
On 10/22/2014 05:45 PM, Krzysztof Kozlowski wrote:
> The driver was requesting all MUIC interrupts but then was masking most
> of them manually at end of probe (with default_init_data). Since
> default_init_data cannot be passed through DTS (no bindings for driver),
> this was a conflicting behavior. First get everything, then mask what we
> don't want.
>
> This could change after adding DTS bindings for requesting specific
> MUIC interrupts. Until then driver should request only these MUIC
> interrupts which he is really interested in.
>
> The commit does not introduce any functional change when the driver is
> used with DTS (no platform data). However this changes the behavior with
> platform data supplied. In such case the driver will request only 3
> interrupts (ADC, ADC1K, ChgTyp). Platform data could still unmask other
> interrupts but they won't be handled by the driver.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> ---
> drivers/extcon/extcon-max77693.c | 26 --------------------------
> 1 file changed, 26 deletions(-)
>
> diff --git a/drivers/extcon/extcon-max77693.c b/drivers/extcon/extcon-max77693.c
> index 863d088c9bdd..9d21e75a7032 100644
> --- a/drivers/extcon/extcon-max77693.c
> +++ b/drivers/extcon/extcon-max77693.c
> @@ -44,19 +44,6 @@ static struct max77693_reg_data default_init_data[] = {
> .addr = MAX77693_MUIC_REG_STATUS2,
> .data = STATUS2_CHGDETRUN_MASK,
> }, {
> - /* INTMASK1 - Unmask [3]ADC1KM,[0]ADCM */
> - .addr = MAX77693_MUIC_REG_INTMASK1,
> - .data = INTMASK1_ADC1K_MASK
> - | INTMASK1_ADC_MASK,
> - }, {
> - /* INTMASK2 - Unmask [0]ChgTypM */
> - .addr = MAX77693_MUIC_REG_INTMASK2,
> - .data = INTMASK2_CHGTYP_MASK,
> - }, {
> - /* INTMASK3 - Mask all of interrupts */
> - .addr = MAX77693_MUIC_REG_INTMASK3,
> - .data = 0x0,
> - }, {
> /* CDETCTRL2 */
> .addr = MAX77693_MUIC_REG_CDETCTRL2,
> .data = CDETCTRL2_VIDRMEN_MASK
> @@ -135,21 +122,8 @@ struct max77693_muic_irq {
>
> static struct max77693_muic_irq muic_irqs[] = {
> { MAX77693_MUIC_IRQ_INT1_ADC, "muic-ADC" },
> - { MAX77693_MUIC_IRQ_INT1_ADC_LOW, "muic-ADCLOW" },
> - { MAX77693_MUIC_IRQ_INT1_ADC_ERR, "muic-ADCError" },
> { MAX77693_MUIC_IRQ_INT1_ADC1K, "muic-ADC1K" },
> { MAX77693_MUIC_IRQ_INT2_CHGTYP, "muic-CHGTYP" },
> - { MAX77693_MUIC_IRQ_INT2_CHGDETREUN, "muic-CHGDETREUN" },
> - { MAX77693_MUIC_IRQ_INT2_DCDTMR, "muic-DCDTMR" },
> - { MAX77693_MUIC_IRQ_INT2_DXOVP, "muic-DXOVP" },
> - { MAX77693_MUIC_IRQ_INT2_VBVOLT, "muic-VBVOLT" },
> - { MAX77693_MUIC_IRQ_INT2_VIDRM, "muic-VIDRM" },
> - { MAX77693_MUIC_IRQ_INT3_EOC, "muic-EOC" },
> - { MAX77693_MUIC_IRQ_INT3_CGMBC, "muic-CGMBC" },
> - { MAX77693_MUIC_IRQ_INT3_OVP, "muic-OVP" },
> - { MAX77693_MUIC_IRQ_INT3_MBCCHG_ERR, "muic-MBCCHG_ERR" },
> - { MAX77693_MUIC_IRQ_INT3_CHG_ENABLED, "muic-CHG_ENABLED" },
> - { MAX77693_MUIC_IRQ_INT3_BAT_DET, "muic-BAT_DET" },
> };
>
> /* Define supported accessory type */
>
next prev parent reply other threads:[~2014-10-22 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 8:45 [PATCH RESEND 1/3] extcon: max77693: Remove left-over code after switching to regmap irq chip Krzysztof Kozlowski
2014-10-22 8:45 ` [PATCH RESEND 2/3] extcon: max77693: Request only specific interrupts Krzysztof Kozlowski
2014-10-22 9:04 ` Chanwoo Choi [this message]
2014-10-22 9:16 ` Krzysztof Kozlowski
2014-10-22 8:45 ` [PATCH RESEND 3/3] extcon: max77693: Fix extcon UART on Trats2 board Krzysztof Kozlowski
2014-10-22 9:09 ` Chanwoo Choi
2014-10-22 9:13 ` 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=5447730E.80500@samsung.com \
--to=cw00.choi@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=myungjoo.ham@samsung.com \
--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