Re: [PATCH v5 2/4] pinctrl: qcom: No need to read-modify-write the interrupt status

2021-01-14 Thread Bjorn Andersson
On Fri 08 Jan 11:35 CST 2021, Douglas Anderson wrote: > When the Qualcomm pinctrl driver wants to Ack an interrupt, it does a > read-modify-write on the interrupt status register. On some SoCs it > makes sure that the status bit is 1 to "Ack" and on others it makes > sure that the bit is 0 to

Re: [PATCH v5 2/4] pinctrl: qcom: No need to read-modify-write the interrupt status

2021-01-13 Thread Stephen Boyd
Quoting Douglas Anderson (2021-01-08 09:35:14) > When the Qualcomm pinctrl driver wants to Ack an interrupt, it does a > read-modify-write on the interrupt status register. On some SoCs it > makes sure that the status bit is 1 to "Ack" and on others it makes > sure that the bit is 0 to "Ack".

Re: [PATCH v5 2/4] pinctrl: qcom: No need to read-modify-write the interrupt status

2021-01-11 Thread Maulik Shah
Hi Doug, Reviewed-by: Maulik Shah Tested-by: Maulik Shah Thanks, Maulik On 1/8/2021 11:05 PM, Douglas Anderson wrote: When the Qualcomm pinctrl driver wants to Ack an interrupt, it does a read-modify-write on the interrupt status register. On some SoCs it makes sure that the status bit is

[PATCH v5 2/4] pinctrl: qcom: No need to read-modify-write the interrupt status

2021-01-08 Thread Douglas Anderson
When the Qualcomm pinctrl driver wants to Ack an interrupt, it does a read-modify-write on the interrupt status register. On some SoCs it makes sure that the status bit is 1 to "Ack" and on others it makes sure that the bit is 0 to "Ack". Presumably the first type of interrupt controller is a