Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

2018-01-02 Thread Chanwoo Choi
Hi Hans, On 2018년 01월 03일 09:58, Chanwoo Choi wrote: > Hi Hans, > > On 2018년 01월 03일 07:44, Hans de Goede wrote: >> Hi, >> >> On 02-01-18 01:54, Chanwoo Choi wrote: >>> Hi Hans, >>> >>> s/dection/detection on patch title. >> >> Thank you for all the reviews. >> >> I've fixed the typo in my person

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

2018-01-02 Thread Chanwoo Choi
Hi Hans, On 2018년 01월 03일 07:44, Hans de Goede wrote: > Hi, > > On 02-01-18 01:54, Chanwoo Choi wrote: >> Hi Hans, >> >> s/dection/detection on patch title. > > Thank you for all the reviews. > > I've fixed the typo in my personal tree. > >> On 2017년 12월 22일 21:36, Hans de Goede wrote: >>> The

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

2018-01-02 Thread Hans de Goede
Hi, On 02-01-18 01:54, Chanwoo Choi wrote: Hi Hans, s/dection/detection on patch title. Thank you for all the reviews. I've fixed the typo in my personal tree. On 2017년 12월 22일 21:36, Hans de Goede wrote: The axp288 extcon code depends on other drivers to do things like mux the data lines

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

2018-01-01 Thread Chanwoo Choi
Hi Hans, s/dection/detection on patch title. On 2017년 12월 22일 21:36, Hans de Goede wrote: > The axp288 extcon code depends on other drivers to do things like mux the > data lines, enable/disable vbus based on the id-pin, etc. > > Sometimes the BIOS has not set these things up correctly resulting

[PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

2017-12-22 Thread Hans de Goede
The axp288 extcon code depends on other drivers to do things like mux the data lines, enable/disable vbus based on the id-pin, etc. Sometimes the BIOS has not set these things up correctly resulting in the initial charger cable type detection giving a wrong result and we end up not charging or cha