From: Hans de Goede <hdegoede@redhat.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH resend v5 3/3] platform/x86: intel_cht_int33fe: Update fusb302 type string, add properties
Date: Fri, 27 Oct 2017 12:13:23 +0200 [thread overview]
Message-ID: <5f747f91-0eb8-5566-5de3-b5dfd1f134ce@redhat.com> (raw)
In-Reply-To: <20171026203323.w5xj2mms5epda6pt@ninjato>
Hi,
On 26-10-17 22:33, Wolfram Sang wrote:
> On Wed, Oct 11, 2017 at 11:41:21AM +0200, Hans de Goede wrote:
>> The fusb302 driver as merged in staging uses "typec_fusb302" as i2c-id
>> rather then just "fusb302" and needs us to set a number of device-
>> properties, adjust the intel_cht_int33fe driver accordingly.
>>
>> One of the properties set is max-snk-mv which makes the fusb302 driver
>> negotiate up to 12V charging voltage, which is a bad idea on boards
>> which are not setup to handle this, so this commit also adds 2 extra
>> sanity checks to make sure that the expected Whiskey Cove PMIC +
>> TI bq24292i charger combo, which can handle 12V, is present.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com>
>
> I can't apply this one. Is there an immutable branch I need to pick up?
> Or shall this go via another tree? My base is v4.14-rc5.
It should be applied on top of this patch:
http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git/commitdiff/5c003458db40cf3c89aeddd22c6e934c28b5a565
From linux-platform-drivers-x86.git/for-next.
So either we are going to need an immutable branch from you
with the first patch of this series so that the platform/x86
maintainers can merge this, or the other way around :|
Regards,
Hans
next prev parent reply other threads:[~2017-10-27 10:13 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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
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=5f747f91-0eb8-5566-5de3-b5dfd1f134ce@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--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
all inboxes | Powered by JetHome®