From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
"Krogerus, Heikki" <heikki.krogerus@linux.intel.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger
Date: Sat, 14 Oct 2017 14:04:11 +0200 [thread overview]
Message-ID: <e875d3d3-d62c-7363-e596-9c0dbeadce5d@redhat.com> (raw)
In-Reply-To: <CAHp75VeqskRsmedvA3eAx27o8WeZzH44880T=Q=+1mD+1nSSAg@mail.gmail.com>
Hi,
On 14-10-17 12:45, Andy Shevchenko wrote:
> On Wed, Oct 11, 2017 at 12:41 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi All,
>>
>> These are the last 3 patches from all my work to add support for
>> USB PD charging to Intel Cherry Trail devices with a Whiskey Cove PMIC
>> and fusb302 Type-C controller.
>>
>> With these 3 patches these devices change from slowly discharging
>> at 5V 0.5A to actually charging at 12V 2A, so getting these upstream
>> is important for users of these devices.
>>
>> Wolfram does not really have time to review the first 2 patches, so if
>> someone else (from the people in the Cc) can review the first 2 patches
>> and esp. the first patch, so that we can get this merged for 4.15, then
>> that would be great.
>
> The person comes to my mind is Heikki,
> Though I dunno he has time either.
The first patch, although it is an i2c-core change, is really
quite simple. I believe anyone can review it. But it does need
someone other then me to take a proper look (and not just do
a code only review) because it is a core change. Maybe there
is another way to solve the problem (persistent / predictable
device-names for i2c devices instantiated through board-data),
but I don't think so.
Also note this is all kernel internal stuff, so we can always
change it later. Although it would be better to get it right in
one go.
Regards,
Hans
next prev parent reply other threads:[~2017-10-14 12:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:41 [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Hans de Goede
2017-10-11 9:41 ` [PATCH resend v5 1/3] i2c: Allow overriding dev_name through board_info Hans de Goede
2017-10-26 20:29 ` Wolfram Sang
2017-10-11 9:41 ` [PATCH resend v5 2/3] i2c-cht-wc: Add device-properties for fusb302 integration Hans de Goede
2017-10-26 20:30 ` Wolfram Sang
2017-10-11 9:41 ` [PATCH resend v5 3/3] platform/x86: intel_cht_int33fe: Update fusb302 type string, add properties Hans de Goede
2017-10-26 20:33 ` Wolfram Sang
2017-10-27 10:13 ` Hans de Goede
2017-10-27 10:31 ` Hans de Goede
2017-10-27 10:41 ` Wolfram Sang
2017-10-27 15:24 ` Hans de Goede
2017-11-03 11:55 ` Andy Shevchenko
2017-10-14 10:45 ` [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Andy Shevchenko
2017-10-14 12:04 ` Hans de Goede [this message]
2017-10-19 14:42 ` Wolfram Sang
2017-10-19 14:54 ` Hans de Goede
2017-10-20 16:36 ` Andy Shevchenko
2017-10-21 8:33 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2017-09-04 13:47 Hans de Goede
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=e875d3d3-d62c-7363-e596-9c0dbeadce5d@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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).