From: "Pali Rohár" <pali.rohar@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Mario Limonciello <mario_limonciello@dell.com>,
Wolfram Sang <wsa@the-dreams.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jean Delvare <jdelvare@suse.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR
Date: Sat, 7 May 2016 16:11:45 +0200 [thread overview]
Message-ID: <201605071611.45664@pali> (raw)
In-Reply-To: <CALCETrW3i7QkVNRo4RQkRViPBo8dSn=4mKDZiA=Ar3v7=dgz1A@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1195 bytes --]
On Friday 06 May 2016 21:00:25 Andy Lutomirski wrote:
> On May 5, 2016 1:27 AM, "Pali Rohár" <pali.rohar@gmail.com> wrote:
> > On Friday 29 April 2016 17:56:14 Andy Lutomirski wrote:
> > > On Fri, Apr 29, 2016 at 2:42 PM, Andy Lutomirski
> > > <luto@amacapital.net>
>
> wrote:
> > > > On Fri, Apr 29, 2016 at 2:00 PM, Pali Rohár
> > > > <pali.rohar@gmail.com>
>
> wrote:
> > > >> On Friday 29 April 2016 20:10:23 Andy Lutomirski wrote:
> > > >>> Jean and Wolfram: is there a quirk mechanism to add i2c
> > > >>> devices that aren't directly enumerable but are known to
> > > >>> exist due to DMI?
> > > >>
> > > >> Maybe something like i2c_register_board_info()?
> > > >
> > > > Maybe. i think that wants to be called before the adapter
> > > > shows up,
>
> though.
>
> > > i2c_probe_optional_slaves may be a more appropriate place to put
> > > this.
> >
> > I cannot find function i2c_probe_optional_slaves. Where is it?
>
> Sorry, I meant i801_probe_optional_slaves.
Hm... that could probably work. I will look at dell-smo8800.c and
lis3lv02d_i2c.c and i2c-i801.c how to interconnect all those devices...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2016-05-07 14:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 10:23 [PATCH] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR Mika Westerberg
2016-04-28 18:34 ` Andy Lutomirski
2016-04-29 8:56 ` Mika Westerberg
2016-04-30 1:13 ` Andy Lutomirski
2016-05-02 10:12 ` Mika Westerberg
2016-05-02 11:42 ` Rafael J. Wysocki
2016-05-02 12:40 ` Mika Westerberg
2016-05-02 15:29 ` Andy Lutomirski
2016-05-02 15:50 ` Mika Westerberg
2016-05-02 15:53 ` Andy Lutomirski
2016-05-02 21:29 ` Rafael J. Wysocki
2016-05-03 8:53 ` Mika Westerberg
2016-04-29 9:03 ` Pali Rohár
2016-04-29 18:10 ` Andy Lutomirski
2016-04-29 21:00 ` Pali Rohár
2016-04-29 21:42 ` Andy Lutomirski
2016-04-30 0:56 ` Andy Lutomirski
2016-04-30 8:12 ` Pali Rohár
2016-05-05 8:27 ` Pali Rohár
[not found] ` <CALCETrW3i7QkVNRo4RQkRViPBo8dSn=4mKDZiA=Ar3v7=dgz1A@mail.gmail.com>
2016-05-07 14:11 ` Pali Rohár [this message]
2016-05-07 15:06 ` Jean Delvare
2016-04-29 20:21 ` Rafael J. Wysocki
2016-05-02 10:21 ` Mika Westerberg
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=201605071611.45664@pali \
--to=pali.rohar@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mario_limonciello@dell.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--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 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).