Skip to contentSkip to conversation

ARM: hisi: soc changes for v4.8

GIT PULL Wei Xu 2 participants 5 messages Jun 28, 2016 – Jul 7, 2016

lore
Share & tools
lore

Wei Xu

author
#0 lore raw

Hi Arnd, Hi Olof, Hi Kevin,

Please help to pull the following changes.
Thanks!

Best Regards,
Wei

---

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.8

for you to fetch changes up to c90047616d4411ff6e7a8a40ed87731dda0753b9:

ARM: hisi: add compatible string for Hi3519 soc (2016-06-28 16:24:33 +0100)

----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.8

- Add initial support for the hi3519 SoC based on armv7
- Avoid the compiling warning by making unexported symbols static

----------------------------------------------------------------
Ben Dooks (1):
ARM: hisi: make unexported symbols static

Jiancheng Xue (1):
ARM: hisi: add compatible string for Hi3519 soc

 arch/arm/mach-hisi/hisilicon.c | 23 ++++-------------------
 arch/arm/mach-hisi/platsmp.c   |  4 ++--
 2 files changed, 6 insertions(+), 21 deletions(-)
#1 lore raw

Hi,

Quoted 28 lines · Wei Xu

Hi Arnd, Hi Olof, Hi Kevin,

Please help to pull the following changes.
Thanks!

Best Regards,
Wei

---

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.8

for you to fetch changes up to c90047616d4411ff6e7a8a40ed87731dda0753b9:

ARM: hisi: add compatible string for Hi3519 soc (2016-06-28 16:24:33 +0100)

----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.8

- Add initial support for the hi3519 SoC based on armv7
- Avoid the compiling warning by making unexported symbols static

Quoted 6 lines

----------------------------------------------------------------
Ben Dooks (1):
ARM: hisi: make unexported symbols static

Jiancheng Xue (1):
ARM: hisi: add compatible string for Hi3519 soc

This patch does more than this, it consolidates a bunch of machine entries.

Since none of them are needed (the generic machine will match instead), just remove all of them instead, please.

I'd recommend a future cleanup to do this instead, as I did for Qualcomm, but since you're already churning this code it's better to do it now.

So, please respin this pull request with the above addressed.

Thanks,

-Olof

author
#2 lore raw

Hi Olof,

Quoted 40 lines · Olof Johansson

Hi,

Quoted 28 lines · Wei Xu

Hi Arnd, Hi Olof, Hi Kevin,

Please help to pull the following changes.
Thanks!

Best Regards,
Wei

---

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.8

for you to fetch changes up to c90047616d4411ff6e7a8a40ed87731dda0753b9:

ARM: hisi: add compatible string for Hi3519 soc (2016-06-28 16:24:33 +0100)

----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.8

- Add initial support for the hi3519 SoC based on armv7
- Avoid the compiling warning by making unexported symbols static

Quoted 6 lines

----------------------------------------------------------------
Ben Dooks (1):
ARM: hisi: make unexported symbols static

Jiancheng Xue (1):
ARM: hisi: add compatible string for Hi3519 soc

This patch does more than this, it consolidates a bunch of machine entries.

Quoted 7 lines

Since none of them are needed (the generic machine will match instead), just remove all of them instead, please.

I'd recommend a future cleanup to do this instead, as I did for Qualcomm, but since you're already churning this code it's better to do it now.

So, please respin this pull request with the above addressed.

There is a specific "map_io" for hi3620 so that we kept 2 machine entries. Do you mean we need to merge all of them in one machine entry? In that case, I will add a new "hisilicon_map_io" function to invoke "debug_ll_io_init" and check the board compatible string.
Is it OK?
Thanks!

Best Regards,
Wei

Quoted 8 lines

Thanks,

-Olof

.

#3 lore raw
Quoted 49 lines · Wei Xu

Hi Olof,

Quoted 46 lines · Olof Johansson

Hi,

Quoted 28 lines · Wei Xu

Hi Arnd, Hi Olof, Hi Kevin,

Please help to pull the following changes.
Thanks!

Best Regards,
Wei

---

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.8

for you to fetch changes up to c90047616d4411ff6e7a8a40ed87731dda0753b9:

ARM: hisi: add compatible string for Hi3519 soc (2016-06-28 16:24:33 +0100)

----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.8

- Add initial support for the hi3519 SoC based on armv7
- Avoid the compiling warning by making unexported symbols static

Quoted 6 lines

----------------------------------------------------------------
Ben Dooks (1):
ARM: hisi: make unexported symbols static

Jiancheng Xue (1):
ARM: hisi: add compatible string for Hi3519 soc

This patch does more than this, it consolidates a bunch of machine entries.

Since none of them are needed (the generic machine will match instead), just remove all of them instead, please.

I'd recommend a future cleanup to do this instead, as I did for Qualcomm, but since you're already churning this code it's better to do it now.

Quoted 7 lines
Quoted 1 line

So, please respin this pull request with the above addressed.

There is a specific "map_io" for hi3620 so that we kept 2 machine entries. Do you mean we need to merge all of them in one machine entry? In that case, I will add a new "hisilicon_map_io" function to invoke "debug_ll_io_init" and check the board compatible string.
Is it OK?

I mean that you only need one machine entry: The one that needs map_io. The others don't need a machine entry at all; they'll be handled by the generic entry in arch/arm/kernel/devtree.c.

-Olof

author
#4 lore raw

Hi Olof,

Quoted 58 lines · Olof Johansson
Quoted 49 lines · Wei Xu

Hi Olof,

Quoted 46 lines · Olof Johansson

Hi,

Quoted 28 lines · Wei Xu

Hi Arnd, Hi Olof, Hi Kevin,

Please help to pull the following changes.
Thanks!

Best Regards,
Wei

---

The following changes since commit 1a695a905c18548062509178b98bc91e67510864:

Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)

are available in the git repository at:

git://github.com/hisilicon/linux-hisi.git tags/hisi-armv7-soc-for-4.8

for you to fetch changes up to c90047616d4411ff6e7a8a40ed87731dda0753b9:

ARM: hisi: add compatible string for Hi3519 soc (2016-06-28 16:24:33 +0100)

----------------------------------------------------------------
ARM: mach-hisi: Hisilicon SoC updates for 4.8

- Add initial support for the hi3519 SoC based on armv7
- Avoid the compiling warning by making unexported symbols static

Quoted 6 lines

----------------------------------------------------------------
Ben Dooks (1):
ARM: hisi: make unexported symbols static

Jiancheng Xue (1):
ARM: hisi: add compatible string for Hi3519 soc

This patch does more than this, it consolidates a bunch of machine entries.

Since none of them are needed (the generic machine will match instead), just remove all of them instead, please.

I'd recommend a future cleanup to do this instead, as I did for Qualcomm, but since you're already churning this code it's better to do it now.

Quoted 7 lines
Quoted 1 line

So, please respin this pull request with the above addressed.

There is a specific "map_io" for hi3620 so that we kept 2 machine entries. Do you mean we need to merge all of them in one machine entry? In that case, I will add a new "hisilicon_map_io" function to invoke "debug_ll_io_init" and check the board compatible string.
Is it OK?

Quoted 3 lines

I mean that you only need one machine entry: The one that needs map_io. The others don't need a machine entry at all; they'll be handled by the generic entry in arch/arm/kernel/devtree.c.

Thanks!
Please ignore the v2 pull request about this.
I will send the v3 today.

Best Regards,
Wei

Quoted 6 lines

-Olof

.