From: David Miller <davem@davemloft.net>
To: bongsu.jeon2@gmail.com
Cc: krzk@kernel.org, linux-nfc@lists.01.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bongsu.jeon@samsung.com
Subject: Re: [PATCH v2 net-next 0/2] nfc: s3fwrn5: Change I2C interrupt trigger to EDGE_RISING
Date: Wed, 09 Dec 2020 16:52:53 -0800 (PST) [thread overview]
Message-ID: <20201209.165253.120704618605367403.davem@davemloft.net> (raw)
In-Reply-To: <20201208141012.6033-1-bongsu.jeon@samsung.com>
From: Bongsu Jeon <bongsu.jeon2@gmail.com>
Date: Tue, 8 Dec 2020 23:10:10 +0900
> From: Bongsu Jeon <bongsu.jeon@samsung.com>
>
> For stable Samsung's I2C interrupt handling, I changed the interrupt
> trigger from IRQ_TYPE_LEVEL_HIGH to IRQ_TYPE_EDGE_RISING and removed
> the hard coded interrupt trigger type in the i2c module for the flexible
> control.
>
> 1/2 is the changed dt binding for the edge rising trigger.
> 2/2 is to remove the hard coded interrupt trigger type in the i2c module.
>
> ChangeLog:
> v2:
> 2/2
> - remove the hard coded interrupt trigger type.
Series applied, thanks.
prev parent reply other threads:[~2020-12-10 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 14:10 [PATCH v2 net-next 0/2] nfc: s3fwrn5: Change I2C interrupt trigger to EDGE_RISING Bongsu Jeon
2020-12-08 14:10 ` [PATCH v2 net-next 1/2] dt-bindings: net: nfc: s3fwrn5: Change I2C interrupt trigger type Bongsu Jeon
2020-12-08 14:10 ` [PATCH v2 net-next 2/2] nfc: s3fwrn5: Remove hard coded interrupt trigger type from the i2c module Bongsu Jeon
2020-12-10 8:18 ` Krzysztof Kozlowski
2020-12-10 0:52 ` David Miller [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=20201209.165253.120704618605367403.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bongsu.jeon2@gmail.com \
--cc=bongsu.jeon@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=netdev@vger.kernel.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).