Message ID | 20171011094121.6108-1-hdegoede@redhat.com |
---|---|
Headers | show |
Series | i2c: Hookup typec power-negotation to the PMIC and charger | expand |
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.
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
> 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. My plan is to hopefully meet Mark Brown (SPI and regulator maintainer) at ELCE next week and have a chat with him about this series. If all goes well, I'll merge it for v4.15.
Hi, On 19-10-17 16:42, Wolfram Sang wrote: > >> 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. > > My plan is to hopefully meet Mark Brown (SPI and regulator maintainer) > at ELCE next week and have a chat with him about this series. If all > goes well, I'll merge it for v4.15. Great, thank you for looking into this. Regards, Hans
On Thu, 2017-10-19 at 16:42 +0200, Wolfram Sang wrote: > > 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. > > My plan is to hopefully meet Mark Brown (SPI and regulator maintainer) > at ELCE next week and have a chat with him about this series. If you don't mind I would like to join. (Yes, I will be at ELC next week) > If all > goes well, I'll merge it for v4.15.
Hi Andy, > > My plan is to hopefully meet Mark Brown (SPI and regulator maintainer) > > at ELCE next week and have a chat with him about this series. > > If you don't mind I would like to join. (Yes, I will be at ELC next > week) Good news! Yes, sure, I'd be glad. Regards, Wolfram