On Saturday, July 09, 2016 11:44:47 AM Hanjun Guo wrote:
> On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
> > On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
> >
> > [...]
> >
> >>> Anyway let's avoid these petty arguments, I agree there must be some
> >>> sort of ARM64 ACPI maintai
On 2016/7/8 21:22, Lorenzo Pieralisi wrote:
On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
[...]
Anyway let's avoid these petty arguments, I agree there must be some
sort of ARM64 ACPI maintainership for the reasons you mentioned above.
To avoid confusion on who's going t
On 2016/7/7 21:58, Rafael J. Wysocki wrote:
On Thursday, July 07, 2016 02:40:23 PM Lorenzo Pieralisi wrote:
[+Sudeep]
On Thu, Jul 07, 2016 at 02:03:17PM +0200, Rafael J. Wysocki wrote:
[...]
So is this a documentation issue in which case Fu Wei can add that to
the file to explain its limited
On 08/07/16 14:22, Lorenzo Pieralisi wrote:
On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
[...]
Anyway let's avoid these petty arguments, I agree there must be some
sort of ARM64 ACPI maintainership for the reasons you mentioned above.
To avoid confusion on who's going
On Thu, Jul 07, 2016 at 03:58:04PM +0200, Rafael J. Wysocki wrote:
[...]
> > Anyway let's avoid these petty arguments, I agree there must be some
> > sort of ARM64 ACPI maintainership for the reasons you mentioned above.
>
> To avoid confusion on who's going to push stuff to Linus, I can do
> th
Hi Rafael,
On 7 July 2016 at 21:58, Rafael J. Wysocki wrote:
> On Thursday, July 07, 2016 02:40:23 PM Lorenzo Pieralisi wrote:
>> [+Sudeep]
>>
>> On Thu, Jul 07, 2016 at 02:03:17PM +0200, Rafael J. Wysocki wrote:
>>
>> [...]
>>
>> > > >> So is this a documentation issue in which case Fu Wei can a
On Thursday, July 07, 2016 02:40:23 PM Lorenzo Pieralisi wrote:
> [+Sudeep]
>
> On Thu, Jul 07, 2016 at 02:03:17PM +0200, Rafael J. Wysocki wrote:
>
> [...]
>
> > > >> So is this a documentation issue in which case Fu Wei can add that to
> > > >> the file to explain its limited to ARM64. Or we c
[+Sudeep]
On Thu, Jul 07, 2016 at 02:03:17PM +0200, Rafael J. Wysocki wrote:
[...]
> > >> So is this a documentation issue in which case Fu Wei can add that to
> > >> the file to explain its limited to ARM64. Or we could even rename the
> > >> file acpi_arm64_gtdt.c
> > >>
> > >> It seems a pity
On Thursday, July 07, 2016 07:12:38 PM Hanjun Guo wrote:
> On 2016/7/6 8:00, Rafael J. Wysocki wrote:
> > On Tue, Jul 5, 2016 at 4:18 PM, Graeme Gregory wrote:
> >> On Mon, Jul 04, 2016 at 02:53:20PM +0200, Rafael J. Wysocki wrote:
> >>> On Fri, Jul 1, 2016 at 11:04 PM, Rafael J. Wysocki
> >>> w
On 2016/7/6 8:00, Rafael J. Wysocki wrote:
On Tue, Jul 5, 2016 at 4:18 PM, Graeme Gregory wrote:
On Mon, Jul 04, 2016 at 02:53:20PM +0200, Rafael J. Wysocki wrote:
On Fri, Jul 1, 2016 at 11:04 PM, Rafael J. Wysocki wrote:
On Friday, July 01, 2016 04:23:40 PM Will Deacon wrote:
On Thu, Jun 3
On Tue, Jul 5, 2016 at 4:18 PM, Graeme Gregory wrote:
> On Mon, Jul 04, 2016 at 02:53:20PM +0200, Rafael J. Wysocki wrote:
>> On Fri, Jul 1, 2016 at 11:04 PM, Rafael J. Wysocki
>> wrote:
>> > On Friday, July 01, 2016 04:23:40 PM Will Deacon wrote:
>> >> On Thu, Jun 30, 2016 at 09:48:02PM +0800,
On Mon, Jul 04, 2016 at 02:53:20PM +0200, Rafael J. Wysocki wrote:
> On Fri, Jul 1, 2016 at 11:04 PM, Rafael J. Wysocki wrote:
> > On Friday, July 01, 2016 04:23:40 PM Will Deacon wrote:
> >> On Thu, Jun 30, 2016 at 09:48:02PM +0800, Hanjun Guo wrote:
> >> > On 2016/6/30 21:27, Rafael J. Wysocki w
On Mon, Jul 4, 2016 at 3:43 PM, Daniel Lezcano
wrote:
> On 07/01/2016 11:01 PM, Rafael J. Wysocki wrote:
>> On Friday, July 01, 2016 04:00:34 PM Daniel Lezcano wrote:
>>> On 06/30/2016 03:27 PM, Rafael J. Wysocki wrote:
>>>
>
> [ ... ]
>
>>> clocksource-probe which is DT based with different drive
On 07/01/2016 11:01 PM, Rafael J. Wysocki wrote:
> On Friday, July 01, 2016 04:00:34 PM Daniel Lezcano wrote:
>> On 06/30/2016 03:27 PM, Rafael J. Wysocki wrote:
>>
[ ... ]
>> clocksource-probe which is DT based with different drivers using it in
>> drivers/clocksource with a pletore of differen
On Fri, Jul 1, 2016 at 11:04 PM, Rafael J. Wysocki wrote:
> On Friday, July 01, 2016 04:23:40 PM Will Deacon wrote:
>> On Thu, Jun 30, 2016 at 09:48:02PM +0800, Hanjun Guo wrote:
>> > On 2016/6/30 21:27, Rafael J. Wysocki wrote:
>> > >On Thursday, June 30, 2016 10:10:02 AM Hanjun Guo wrote:
>> > >
On Friday, July 01, 2016 04:23:40 PM Will Deacon wrote:
> On Thu, Jun 30, 2016 at 09:48:02PM +0800, Hanjun Guo wrote:
> > On 2016/6/30 21:27, Rafael J. Wysocki wrote:
> > >On Thursday, June 30, 2016 10:10:02 AM Hanjun Guo wrote:
> > >>GTDT is part of ACPI spec, drivers/acpi/ is for driver code of
>
On Friday, July 01, 2016 04:00:34 PM Daniel Lezcano wrote:
> On 06/30/2016 03:27 PM, Rafael J. Wysocki wrote:
>
> [ ... ]
>
> >> GTDT is part of ACPI spec, drivers/acpi/ is for driver code of
> >> ACPI spec, I think it can stay in drivers/acpi/ from this point
> >> of view, am I right?
> >
> > Th
On Thu, Jun 30, 2016 at 09:48:02PM +0800, Hanjun Guo wrote:
> On 2016/6/30 21:27, Rafael J. Wysocki wrote:
> >On Thursday, June 30, 2016 10:10:02 AM Hanjun Guo wrote:
> >>GTDT is part of ACPI spec, drivers/acpi/ is for driver code of
> >>ACPI spec, I think it can stay in drivers/acpi/ from this poi
On 06/30/2016 03:27 PM, Rafael J. Wysocki wrote:
[ ... ]
GTDT is part of ACPI spec, drivers/acpi/ is for driver code of
ACPI spec, I think it can stay in drivers/acpi/ from this point
of view, am I right?
The question is not "Can it?", but "Does it need to?".
It is in the spec, but still the
On 2016/6/30 21:27, Rafael J. Wysocki wrote:
On Thursday, June 30, 2016 10:10:02 AM Hanjun Guo wrote:
Hi Rafael,
On 2016/6/30 9:37, Rafael J. Wysocki wrote:
On Thursday, June 30, 2016 09:29:59 AM Fu Wei wrote:
Hi Rafael,
On 30 June 2016 at 05:32, Rafael J. Wysocki wrote:
On Wed, Jun 29, 20
On Thursday, June 30, 2016 10:10:02 AM Hanjun Guo wrote:
> Hi Rafael,
>
> On 2016/6/30 9:37, Rafael J. Wysocki wrote:
> > On Thursday, June 30, 2016 09:29:59 AM Fu Wei wrote:
> >> Hi Rafael,
> >>
> >> On 30 June 2016 at 05:32, Rafael J. Wysocki wrote:
> >>> On Wed, Jun 29, 2016 at 8:15 PM, wrot
Hi Rafael,
On 2016/6/30 9:37, Rafael J. Wysocki wrote:
On Thursday, June 30, 2016 09:29:59 AM Fu Wei wrote:
Hi Rafael,
On 30 June 2016 at 05:32, Rafael J. Wysocki wrote:
On Wed, Jun 29, 2016 at 8:15 PM, wrote:
From: Fu Wei
This patchset:
(1)Preparation for adding GTDT support in arm
On Thursday, June 30, 2016 09:29:59 AM Fu Wei wrote:
> Hi Rafael,
>
> On 30 June 2016 at 05:32, Rafael J. Wysocki wrote:
> > On Wed, Jun 29, 2016 at 8:15 PM, wrote:
> >> From: Fu Wei
> >>
> >> This patchset:
> >> (1)Preparation for adding GTDT support in arm_arch_timer
> >> 1. Move
Hi Rafael,
On 30 June 2016 at 05:32, Rafael J. Wysocki wrote:
> On Wed, Jun 29, 2016 at 8:15 PM, wrote:
>> From: Fu Wei
>>
>> This patchset:
>> (1)Preparation for adding GTDT support in arm_arch_timer
>> 1. Move some enums and marcos to header file
>> 2. Add a new enum for
On Wed, Jun 29, 2016 at 8:15 PM, wrote:
> From: Fu Wei
>
> This patchset:
> (1)Preparation for adding GTDT support in arm_arch_timer
> 1. Move some enums and marcos to header file
> 2. Add a new enum for spi type.
> 3. Improve printk relevant code
>
> (2)Introduce
From: Fu Wei
This patchset:
(1)Preparation for adding GTDT support in arm_arch_timer
1. Move some enums and marcos to header file
2. Add a new enum for spi type.
3. Improve printk relevant code
(2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c
Parse all kinds
26 matches
Mail list logo
