Skip to contentSkip to conversation

DT/core: cpu_ofnode updates for v3.12

GIT PULL Sudeep KarkadaNagesha 4 participants 10 messages Aug 6, 2013 – Aug 12, 2013

lore
Share & tools
lore
#0 lore raw

Hi Rob,

The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

are available in the git repository at:

git://linux-arm.org/linux-skn.git cpu_ofnode_dt

for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:

of/device: add helper to get cpu device node from logical cpu index
(2013-08-06 16:37:15 +0100)

----------------------------------------------------------------
Sudeep KarkadaNagesha (4):
of: add support for retrieving cpu node for a given logical cpu index
ARM: DT/kernel: define ARM specific arch_match_cpu_phys_id driver/core: cpu: initialize of_node in cpu's device struture of/device: add helper to get cpu device node from logical cpu index

 arch/arm/kernel/devtree.c |  5 +++++
 drivers/base/cpu.c        |  2 ++
 drivers/of/base.c         | 73 ++++++++++++++++++++++++++++++
 include/linux/cpu.h       |  1 +
 include/linux/of.h        |  6 ++++++
 include/linux/of_device.h | 15 +++++++++++++++
 6 files changed, 102 insertions(+)

PS: This is DT part of the patch series reviewed and acknowledged @

v1:
http://archive.arm.linux.org.uk/lurker/message/20130715.102201.dfb8e04e.fr.html
v2:
http://archive.arm.linux.org.uk/lurker/message/20130717.140609.07fa6237.fr.html
v3:
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html

Regards,
Sudeep

#1 lore raw

Hi Rob,

Quoted 6 lines · Sudeep KarkadaNagesha

Hi Rob,

The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

Quoted 9 lines

are available in the git repository at:

git://linux-arm.org/linux-skn.git cpu_ofnode_dt

for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:

of/device: add helper to get cpu device node from logical cpu index
(2013-08-06 16:37:15 +0100)

I was not sure whom to send pull request(you or Grant). This needs to be pulled in and present in linux-next before I can send the updates in SoC and cpufreq which depends on this.

Regards,
Sudeep

Quoted 28 lines

----------------------------------------------------------------
Sudeep KarkadaNagesha (4):
of: add support for retrieving cpu node for a given logical cpu index
ARM: DT/kernel: define ARM specific arch_match_cpu_phys_id driver/core: cpu: initialize of_node in cpu's device struture of/device: add helper to get cpu device node from logical cpu index

 arch/arm/kernel/devtree.c |  5 +++++
 drivers/base/cpu.c        |  2 ++
 drivers/of/base.c         | 73 ++++++++++++++++++++++++++++++
 include/linux/cpu.h       |  1 +
 include/linux/of.h        |  6 ++++++
 include/linux/of_device.h | 15 +++++++++++++++
 6 files changed, 102 insertions(+)

PS: This is DT part of the patch series reviewed and acknowledged @

v1:
http://archive.arm.linux.org.uk/lurker/message/20130715.102201.dfb8e04e.fr.html
v2:
http://archive.arm.linux.org.uk/lurker/message/20130717.140609.07fa6237.fr.html
v3:
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html

Regards,
Sudeep

#2 lore raw
Quoted 15 lines · Sudeep KarkadaNagesha

Hi Rob,

Quoted 12 lines · Sudeep KarkadaNagesha

Hi Rob,

The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

are available in the git repository at:

git://linux-arm.org/linux-skn.git cpu_ofnode_dt

for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:

Quoted 7 lines
Quoted 3 lines

of/device: add helper to get cpu device node from logical cpu index
(2013-08-06 16:37:15 +0100)

I was not sure whom to send pull request(you or Grant). This needs to be pulled in and present in linux-next before I can send the updates in SoC and cpufreq which depends on this.

With necessary acks, you don't need send these to 3 maintainers. I would suggest you send the whole series to cpufreq maintainers to merge rather than have them try to manage 2 dependent branches.

Also, something landing in linux-next has no bearing on the process. If you do have dependent branches in another tree, then you need to insure with that maintainer that the branch is stable and inform the 2nd maintainer of the dependency on the branch.

Rob

Quoted 34 lines

Regards,
Sudeep

Quoted 28 lines

----------------------------------------------------------------
Sudeep KarkadaNagesha (4):
of: add support for retrieving cpu node for a given logical cpu index
ARM: DT/kernel: define ARM specific arch_match_cpu_phys_id driver/core: cpu: initialize of_node in cpu's device struture of/device: add helper to get cpu device node from logical cpu index

 arch/arm/kernel/devtree.c |  5 +++++
 drivers/base/cpu.c        |  2 ++
 drivers/of/base.c         | 73 ++++++++++++++++++++++++++++++
 include/linux/cpu.h       |  1 +
 include/linux/of.h        |  6 ++++++
 include/linux/of_device.h | 15 +++++++++++++++
 6 files changed, 102 insertions(+)

PS: This is DT part of the patch series reviewed and acknowledged @

v1:
http://archive.arm.linux.org.uk/lurker/message/20130715.102201.dfb8e04e.fr.html
v2:
http://archive.arm.linux.org.uk/lurker/message/20130717.140609.07fa6237.fr.html
v3:
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html

Regards,
Sudeep

#3 lore raw
Quoted 25 lines · Rob Herring
Quoted 15 lines · Sudeep KarkadaNagesha

Hi Rob,

Quoted 12 lines · Sudeep KarkadaNagesha

Hi Rob,

The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

are available in the git repository at:

git://linux-arm.org/linux-skn.git cpu_ofnode_dt

for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:

Quoted 7 lines
Quoted 3 lines

of/device: add helper to get cpu device node from logical cpu index
(2013-08-06 16:37:15 +0100)

I was not sure whom to send pull request(you or Grant). This needs to be pulled in and present in linux-next before I can send the updates in SoC and cpufreq which depends on this.

Quoted 9 lines

With necessary acks, you don't need send these to 3 maintainers. I would suggest you send the whole series to cpufreq maintainers to merge rather than have them try to manage 2 dependent branches.

Also, something landing in linux-next has no bearing on the process. If you do have dependent branches in another tree, then you need to insure with that maintainer that the branch is stable and inform the 2nd maintainer of the dependency on the branch.

Thanks Rob for clarifying.

Hi Rafael,

The complete series[1] was reviewed and acknowledged by appropriate maintainers.

Since most of the changes are CPUFreq clean-ups, would you take the complete series through your tree ?

On which branch(bleeding-edge or linux-next) on [2] do I need to base my pull request ?

Regards,
Sudeep

[1]
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html

[2] git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git

#4 lore raw
Quoted 40 lines · Sudeep KarkadaNagesha
Quoted 25 lines · Rob Herring
Quoted 15 lines · Sudeep KarkadaNagesha

Hi Rob,

Quoted 12 lines · Sudeep KarkadaNagesha

Hi Rob,

The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

are available in the git repository at:

git://linux-arm.org/linux-skn.git cpu_ofnode_dt

for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:

Quoted 7 lines
Quoted 3 lines

of/device: add helper to get cpu device node from logical cpu index
(2013-08-06 16:37:15 +0100)

I was not sure whom to send pull request(you or Grant). This needs to be pulled in and present in linux-next before I can send the updates in SoC and cpufreq which depends on this.

Quoted 9 lines

With necessary acks, you don't need send these to 3 maintainers. I would suggest you send the whole series to cpufreq maintainers to merge rather than have them try to manage 2 dependent branches.

Also, something landing in linux-next has no bearing on the process. If you do have dependent branches in another tree, then you need to insure with that maintainer that the branch is stable and inform the 2nd maintainer of the dependency on the branch.

Thanks Rob for clarifying.

Hi Rafael,

Quoted 8 lines

The complete series[1] was reviewed and acknowledged by appropriate maintainers.

Since most of the changes are CPUFreq clean-ups, would you take the complete series through your tree ?

On which branch(bleeding-edge or linux-next) on [2] do I need to base my pull request ?

Hi Rafael,

Can you please let which know which branch do you prefer to base the my request on ?

Regards,
Sudeep

Quoted 6 lines

[1]
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html

[2] git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git

#5 lore raw
Quoted 2 lines · Sudeep KarkadaNagesha

Can you please let which know which branch do you prefer to base the my request on ?

Unless you have any dependencies, you must rebase on latest RC..

#6 lore raw
Quoted 6 lines · Viresh Kumar
Quoted 2 lines · Sudeep KarkadaNagesha

Can you please let which know which branch do you prefer to base the my request on ?

Unless you have any dependencies, you must rebase on latest RC..

Yes, preferably 3.11-rc5.

If there are any dependencies on linux-next material, please let me know.

Thanks,
Rafael

#7 lore raw

Hi Rafael,

Quoted 12 lines · Rafael J. Wysocki
Quoted 6 lines · Viresh Kumar
Quoted 2 lines · Sudeep KarkadaNagesha

Can you please let which know which branch do you prefer to base the my request on ?

Unless you have any dependencies, you must rebase on latest RC..

Yes, preferably 3.11-rc5.

If there are any dependencies on linux-next material, please let me know.

It doesn't have any functional dependencies, however I just found out now that there's a conflict with today's linux-next branch(tag:
next-20130812)

Regards,
Sudeep

#8 lore raw
Quoted 11 lines · Sudeep KarkadaNagesha

Hi Rafael,

Quoted 8 lines · Rafael J. Wysocki
Quoted 6 lines · Viresh Kumar
Quoted 2 lines · Sudeep KarkadaNagesha

Can you please let which know which branch do you prefer to base the my request on ?

Unless you have any dependencies, you must rebase on latest RC..

Quoted 8 lines
Quoted 4 lines

Yes, preferably 3.11-rc5.

If there are any dependencies on linux-next material, please let me know.

It doesn't have any functional dependencies, however I just found out now that there's a conflict with today's linux-next branch(tag:
next-20130812)

That's not a big deal.

Thanks,
Rafael

Signature · 2 lines
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
#9 lore raw
Quoted 14 lines · Rafael J. Wysocki
Quoted 13 lines · Sudeep KarkadaNagesha

Hi Rafael,

Quoted 10 lines · Rafael J. Wysocki
Quoted 6 lines · Viresh Kumar
Quoted 2 lines · Sudeep KarkadaNagesha

Can you please let which know which branch do you prefer to base the my request on ?

Unless you have any dependencies, you must rebase on latest RC..

Yes, preferably 3.11-rc5.

Quoted 9 lines
Quoted 6 lines
Quoted 2 lines

If there are any dependencies on linux-next material, please let me know.

It doesn't have any functional dependencies, however I just found out now that there's a conflict with today's linux-next branch(tag:
next-20130812)

That's not a big deal.

Thanks Rafael, in that case I will send the pull request based on 3.11-rc5

Regards,
Sudeep