From: Dmitry Torokhov <dtor@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Michał Kępień" <kernel@kempniu.pl>,
"Jean Delvare" <jdelvare@suse.com>,
"Takashi Iwai" <tiwai@suse.de>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: do not enable fall back to Host Notify by default
Date: Thu, 12 Jan 2017 12:33:52 -0800 [thread overview]
Message-ID: <20170112203352.GA17915@dtor-ws> (raw)
In-Reply-To: <20170112184101.slxulrvreq7zl2pc@ninjato>
On Thu, Jan 12, 2017 at 07:41:01PM +0100, Wolfram Sang wrote:
> On Wed, Jan 04, 2017 at 08:57:22PM -0800, Dmitry Torokhov wrote:
> > Falling back unconditionally to HostNotify as primary client's interrupt
> > breaks some drivers which alter their functionality depending on whether
> > interrupt is present or not, so let's introduce a board flag telling I2C
> > core explicitly if we want wired interrupt or HostNotify-based one:
> > I2C_CLIENT_HOST_NOTIFY.
> >
> > For DT-based systems we introduce "host-notify" property that we convert
> > to I2C_CLIENT_HOST_NOTIFY board flag.
> >
> > Tested-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>
> Applied to for-current, thanks!
>
> How do we handle driver fixes? Shall I take them via I2C to have the
> dependency clear? Or can they go seperately?
The drivers that need this will go [hopefully] into next so they should
be OK to go through my tree.
--
Dmitry
prev parent reply other threads:[~2017-01-12 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 4:57 [PATCH v2] i2c: do not enable fall back to Host Notify by default Dmitry Torokhov
2017-01-05 12:39 ` Pali Rohár
2017-01-09 17:56 ` Rob Herring
2017-01-12 18:41 ` Wolfram Sang
2017-01-12 20:33 ` Dmitry Torokhov [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=20170112203352.GA17915@dtor-ws \
--to=dtor@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kernel@kempniu.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.de \
--cc=wsa@the-dreams.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.