[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g45FtwHyfptDEZJ=QJT1uRcwWa6+sHgqaodcNGD4izmT5w@mail.gmail.com>
Date: Tue, 4 Feb 2020 13:05:27 -0800
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Wolfram Sang <wsa@...-dreams.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
linux-i2c@...r.kernel.org, linux-arm-msm@...r.kernel.org,
Girish Mahadevan <girishm@...eaurora.org>,
Dilip Kota <dkota@...eaurora.org>,
Alok Chauhan <alokc@...eaurora.org>,
Douglas Anderson <dianders@...omium.org>
Subject: Re: [PATCH 1/3] i2c: qcom-geni: Let firmware specify irq trigger flags
On Tue, Feb 4, 2020 at 11:32 AM Stephen Boyd <swboyd@...omium.org> wrote:
>
> We don't need to force IRQF_TRIGGER_HIGH here as the DT or ACPI tables
> should take care of this for us. Just use 0 instead so that we use the
> flags from the firmware. Also, remove specify dev_name() for the irq
> name so that we can get better information in /proc/interrupts about
> which device is generating interrupts.
>
> Cc: Girish Mahadevan <girishm@...eaurora.org>
> Cc: Dilip Kota <dkota@...eaurora.org>
> Cc: Alok Chauhan <alokc@...eaurora.org>
> Cc: Douglas Anderson <dianders@...omium.org>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
Reviewed-by: Brendan Higgins <brendanhiggins@...gle.com>
Seems pretty straightforward to me.
Powered by blists - more mailing lists