lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 27 Oct 2017 12:13:23 +0200
From:   Hans de Goede <>
To:     Wolfram Sang <>
Cc:     Darren Hart <>,
        Andy Shevchenko <>,
        Jarkko Nikula <>,
        Andy Shevchenko <>,,,
Subject: Re: [PATCH resend v5 3/3] platform/x86: intel_cht_int33fe: Update
 fusb302 type string, add properties


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 <>
>> Acked-by: Andy Shevchenko <>
> 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:

 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 :|



Powered by blists - more mailing lists