Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-08-01 Thread Matthias Kaehlcke
On Wed, Aug 01, 2018 at 05:18:40PM +0900, Chanwoo Choi wrote: > Hi Matthias, > > On 2018년 08월 01일 04:29, Matthias Kaehlcke wrote: > > On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: > >> Hi Chanwoo, > >> > >> On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > >>>

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-08-01 Thread Matthias Kaehlcke
On Wed, Aug 01, 2018 at 05:18:40PM +0900, Chanwoo Choi wrote: > Hi Matthias, > > On 2018년 08월 01일 04:29, Matthias Kaehlcke wrote: > > On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: > >> Hi Chanwoo, > >> > >> On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > >>>

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-08-01 Thread Chanwoo Choi
Hi Matthias, On 2018년 08월 01일 04:29, Matthias Kaehlcke wrote: > On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: >> Hi Chanwoo, >> >> On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: >>> Hi Matthias, >>> >>> On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: Hi,

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-08-01 Thread Chanwoo Choi
Hi Matthias, On 2018년 08월 01일 04:29, Matthias Kaehlcke wrote: > On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: >> Hi Chanwoo, >> >> On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: >>> Hi Matthias, >>> >>> On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: Hi,

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-31 Thread Matthias Kaehlcke
On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: > Hi Chanwoo, > > On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > > Hi Matthias, > > > > On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > > > Hi, > > > > > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-31 Thread Matthias Kaehlcke
On Mon, Jul 16, 2018 at 12:41:14PM -0700, Matthias Kaehlcke wrote: > Hi Chanwoo, > > On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > > Hi Matthias, > > > > On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > > > Hi, > > > > > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-16 Thread Matthias Kaehlcke
Hi Chanwoo, On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > Hi Matthias, > > On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > > Hi, > > > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > > > >> I didn't see any framework which exporting the class instance. >

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-16 Thread Matthias Kaehlcke
Hi Chanwoo, On Thu, Jul 12, 2018 at 06:08:36PM +0900, Chanwoo Choi wrote: > Hi Matthias, > > On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > > Hi, > > > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > > > >> I didn't see any framework which exporting the class instance. >

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-12 Thread Chanwoo Choi
Hi Matthias, On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > Hi, > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > >> I didn't see any framework which exporting the class instance. >> It is very dangerous. Unknown device drivers is able to reset >> the 'devfreq_class'

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-12 Thread Chanwoo Choi
Hi Matthias, On 2018년 07월 07일 03:09, Matthias Kaehlcke wrote: > Hi, > > On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > >> I didn't see any framework which exporting the class instance. >> It is very dangerous. Unknown device drivers is able to reset >> the 'devfreq_class'

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-06 Thread Matthias Kaehlcke
Hi, On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > I didn't see any framework which exporting the class instance. > It is very dangerous. Unknown device drivers is able to reset > the 'devfreq_class' instance. I can't agree this approach. While I agree that it is potential

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-06 Thread Matthias Kaehlcke
Hi, On Wed, Jul 04, 2018 at 02:30:32PM +0900, Chanwoo Choi wrote: > I didn't see any framework which exporting the class instance. > It is very dangerous. Unknown device drivers is able to reset > the 'devfreq_class' instance. I can't agree this approach. While I agree that it is potential

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-03 Thread Chanwoo Choi
Hi, I didn't see any framework which exporting the class instance. It is very dangerous. Unknown device drivers is able to reset the 'devfreq_class' instance. I can't agree this approach. Regards, Chanwoo Choi On 2018년 07월 04일 08:47, Matthias Kaehlcke wrote: > Exporting the device class allows

Re: [PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-03 Thread Chanwoo Choi
Hi, I didn't see any framework which exporting the class instance. It is very dangerous. Unknown device drivers is able to reset the 'devfreq_class' instance. I can't agree this approach. Regards, Chanwoo Choi On 2018년 07월 04일 08:47, Matthias Kaehlcke wrote: > Exporting the device class allows

[PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-03 Thread Matthias Kaehlcke
Exporting the device class allows other parts of the kernel to enumerate the devfreq devices and receive notification when a devfreq device is added or removed. Signed-off-by: Matthias Kaehlcke Reviewed-by: Brian Norris --- Changes in v5: - none Changes in v4: - added 'Reviewed-by: Brian

[PATCH v5 07/12] PM / devfreq: export devfreq_class

2018-07-03 Thread Matthias Kaehlcke
Exporting the device class allows other parts of the kernel to enumerate the devfreq devices and receive notification when a devfreq device is added or removed. Signed-off-by: Matthias Kaehlcke Reviewed-by: Brian Norris --- Changes in v5: - none Changes in v4: - added 'Reviewed-by: Brian