mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: "Maulik Shah (mkshah)" <quic_mkshah@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] irqchip/qcom-pdc: add support for v3.2 HW
Date: Wed, 23 Aug 2023 11:21:59 +0200	[thread overview]
Message-ID: <725804c1-446e-4bf5-ad89-9300b34aa0c9@linaro.org> (raw)
In-Reply-To: <6613c15b-7951-12b3-cbfd-2961046de2b7@quicinc.com>

On 23/08/2023 11:19, Maulik Shah (mkshah) wrote:
> Hi Neil,
> 
> On 8/23/2023 2:21 PM, neil.armstrong@linaro.org wrote:
>> On 23/08/2023 10:25, Maulik Shah (mkshah) wrote:
>>> Hi,
>>>
>>> On 8/23/2023 1:16 PM, Neil Armstrong wrote:
>>>> Hi,
>>>>
>>>> On 23/08/2023 07:35, Maulik Shah (mkshah) wrote:
>>>>> Hi Neil,
>>>>>
>>>>> @@ -142,8 +163,17 @@ static int qcom_pdc_gic_set_type(struct irq_data *d, unsigned int type)
>>>>>>           return -EINVAL;
>>>>>>       }
>>>>>> -    old_pdc_type = pdc_reg_read(IRQ_i_CFG, d->hwirq);
>>>>>> -    pdc_reg_write(IRQ_i_CFG, d->hwirq, pdc_type);
>>>>>> +    if (pdc_version < PDC_VERSION_3_2) {
>>>>>> +        old_pdc_type = pdc_reg_read(IRQ_i_CFG, d->hwirq);
>>>>>> +        pdc_reg_write(IRQ_i_CFG, d->hwirq, pdc_type);
>>>>>> +    } else {
>>>>>> +        u32 val;
>>>>>> +
>>>>>> +        val = pdc_reg_read(IRQ_i_CFG, d->hwirq);
>>>>>> +        old_pdc_type = val & IRQ_i_CFG_TYPE_MASK;
>>>>>> +        pdc_reg_write(IRQ_i_CFG, d->hwirq,
>>>>>> +                  pdc_type | (val & IRQ_i_CFG_IRQ_ENABLE));
>>>>>> +    }
>>>>> While above is correct, i don't think we need version check in qcom_pdc_gic_set_type() as bits 0-2 are always for the type in old/new version as mentioned in v1.
>>>>>
>>>>> Adding one line after reading old_pdc_type should be good enough.
>>>>
>>>> Yes I understood, but while looking at the IRQ_i_CFG bits, I wanted to keep the original
>>>> driver behavior intact by setting remaining bits to 0.
>>>>
>>>> Adding this single line changes that behavior and keeps bits 3-31
>>>> to the default register value, which may have some consequences.
>>>>
>>>> If you consider it's an ok change, then I'll reduce it to this single line.
>>> Yes this ok change to have single line and should not have  any consequences.
>>
>> I also remember why, it's about the final check:
>>
>> 184         if (old_pdc_type != pdc_type)
>> 185                 irq_chip_set_parent_state(d, IRQCHIP_STATE_PENDING, false);
>>
>> We need to strip out remaining bits of old_pdc_type of this won't work as
>> expected, so I'll change it to :
>>
>> +       old_pdc_type = pdc_reg_read(IRQ_i_CFG, d->hwirq);
>> +       pdc_type |= (old_pdc_type & ~IRQ_i_CFG_TYPE_MASK);
>> +       old_pdc_type &= IRQ_i_CFG_TYPE_MASK;
>> +       pdc_reg_write(IRQ_i_CFG, d->hwirq, pdc_type);
>>
>> Is it ok for you ?
> 
> No.
> 
>          old_pdc_type = pdc_reg_read(IRQ_i_CFG, d->hwirq);
> 
> +       pdc_type |= (old_pdc_type & ~IRQ_i_CFG_TYPE_MASK);
> 
> Adding above suggested single line is sufficient to make final check properly compare both old_pdc_type and new pdc_type, right?
> 
> But with your above change, It will end up comparing only bits 0-2 of old_pdc_type with updated pdc_type (which just got the other bits (3 to 31) of IRQ_i_CFG register by the ORing it with old_pdc_type).

Oh yeah indeed it's right, I had my previous code in mind.

I'll stick with the single line then,

Thanks,
Neil

> 
> Thanks,
> Maulik


      reply	other threads:[~2023-08-23  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  8:31 Neil Armstrong
2023-08-23  5:35 ` Maulik Shah (mkshah)
2023-08-23  7:46   ` Neil Armstrong
2023-08-23  8:25     ` Maulik Shah (mkshah)
2023-08-23  8:51       ` neil.armstrong
2023-08-23  9:19         ` Maulik Shah (mkshah)
2023-08-23  9:21           ` neil.armstrong [this message]

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=725804c1-446e-4bf5-ad89-9300b34aa0c9@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=quic_mkshah@quicinc.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®