Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-10 Thread Atish Patra
On 12/5/18 9:53 AM, Jeffrey Hugo wrote: On 11/29/2018 4:28 PM, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-10 Thread Atish Patra
On 12/7/18 5:45 AM, Morten Rasmussen wrote: Hi, On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-07 Thread Sudeep Holla
On Fri, Dec 07, 2018 at 01:45:21PM +, Morten Rasmussen wrote: > Hi, > > On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote: > > The cpu-map DT entry in ARM64 can describe the CPU topology in > > much better way compared to other existing approaches. RISC-V can > > easily adopt this

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-07 Thread Sudeep Holla
On Fri, Dec 07, 2018 at 01:45:21PM +, Morten Rasmussen wrote: > Hi, > > On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote: > > The cpu-map DT entry in ARM64 can describe the CPU topology in > > much better way compared to other existing approaches. RISC-V can > > easily adopt this

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-07 Thread Morten Rasmussen
Hi, On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote: > The cpu-map DT entry in ARM64 can describe the CPU topology in > much better way compared to other existing approaches. RISC-V can > easily adopt this binding to represent it's own CPU topology. > Thus, both cpu-map DT binding and

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-07 Thread Morten Rasmussen
Hi, On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote: > The cpu-map DT entry in ARM64 can describe the CPU topology in > much better way compared to other existing approaches. RISC-V can > easily adopt this binding to represent it's own CPU topology. > Thus, both cpu-map DT binding and

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-05 Thread Jeffrey Hugo
On 11/29/2018 4:28 PM, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-12-05 Thread Jeffrey Hugo
On 11/29/2018 4:28 PM, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be

[RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-11-29 Thread Atish Patra
The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be moved to a common location so that RISC-V or

[RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

2018-11-29 Thread Atish Patra
The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be moved to a common location so that RISC-V or