From: Rob Herring <robh@kernel.org>
To: allen <allen.chen@ite.com.tw>
Cc: Jau-Chih Tseng <Jau-Chih.Tseng@ite.com.tw>,
Hermes Wu <Hermes.Wu@ite.com.tw>,
Kenneth Hung <Kenneth.Hung@ite.com.tw>,
Pi-Hsun Shih <pihsun@chromium.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Sam Ravnborg <sam@ravnborg.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] ite-it6505 change trigger conditions
Date: Mon, 24 Aug 2020 16:32:07 -0600 [thread overview]
Message-ID: <20200824223126.GA3434984@bogus> (raw)
In-Reply-To: <1597054312-25538-2-git-send-email-allen.chen@ite.com.tw>
On Mon, Aug 10, 2020 at 06:11:15PM +0800, allen wrote:
> it6505 changes trigger conditions.
Patches must have a Signed-off-by with a full name.
> ---
> Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml b/Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml
> index 2c50016..bf0e889 100644
> --- a/Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/ite,it6505.yaml
> @@ -73,7 +73,7 @@ examples:
>
> dp-bridge@5c {
> compatible = "ite,it6505";
> - interrupts = <152 IRQ_TYPE_EDGE_FALLING 152 0>;
> + interrupts = <152 IRQ_TYPE_LEVEL_LOW 152 0>;
How does this have 2 interrupts which are the same irq number, but
different flags?
> reg = <0x5c>;
> pinctrl-names = "default";
> pinctrl-0 = <&it6505_pins>;
> --
> 1.9.1
>
next prev parent reply other threads:[~2020-08-24 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 10:11 [PATCH v1 0/2] IT6505 cover letter allen
2020-08-10 10:11 ` [PATCH v1 1/2] ite-it6505 change trigger conditions allen
2020-08-24 22:32 ` Rob Herring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-10 9:53 [PATCH v1 0/2] IT6505 cover letter allen
2020-08-10 9:53 ` [PATCH v1 1/2] ite-it6505 change trigger conditions allen
2020-08-10 18:27 ` Sam Ravnborg
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=20200824223126.GA3434984@bogus \
--to=robh@kernel.org \
--cc=Hermes.Wu@ite.com.tw \
--cc=Jau-Chih.Tseng@ite.com.tw \
--cc=Kenneth.Hung@ite.com.tw \
--cc=airlied@linux.ie \
--cc=allen.chen@ite.com.tw \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pihsun@chromium.org \
--cc=sam@ravnborg.org \
/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;
as well as URLs for NNTP newsgroup(s).