Comment # 20 on bug 1043231 from Matwey Kornilov

0001-ARM-EXYNOS-Remove-calls-to-of_genpd_get_from_provide.patch is
armv7-specific

0002-mvebu-Use-dev_pm_opp_set_sharing_cpus-to-mark-OPP-ta.patch is
armv7-specific

0003-cpufreq-tegra124-No-need-of-setting-platform-data.patch is armv7-specific
(tegra124 is cortex-a15 based platform)

0004-extcon-adc-jack-Remove-the-usage-of-extcon_set_state.patch
0005-extcon-arizona-Remove-the-usage-of-extcon_update_sta.patch

are required to fix errors like this:

/home/matwey/lab/linux/drivers/extcon/extcon-adc-jack.c: In function
'adc_jack_handler':
/home/matwey/lab/linux/drivers/extcon/extcon-adc-jack.c:81:2: error: too few
arguments to function 'extcon_set_state'
  extcon_set_state(data->edev, state);

and that:

/home/matwey/lab/linux/drivers/extcon/extcon-arizona.c: In function
'arizona_jackdet':
/home/matwey/lab/linux/drivers/extcon/extcon-arizona.c:1152:9: error: implicit
declaration of function 'extcon_update_state'
[-Werror=implicit-function-declaration]
   ret = extcon_update_state(info->edev, 0xffffffff, 0);

which come from API change introduced by patch
rk3399-0010-extcon-Add-the-synchronization-extcon-APIs-to-suppor.patch which is
already in SUSE kernel. And as soon as nobody had checked extcon compilation
when rk3399-0010-extcon-Add-the-synchronization-extcon-APIs-to-suppor.patch was
applied, they are also armv7-specific.

0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch

is required to fix errors like those:

/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c: In function
'max77693_haptic_set_duty_cycle':
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:73:30: error:
'struct pwm_device' has no member named 'period'
  int delta = (haptic->pwm_dev->period + haptic->pwm_duty) / 2;
                              ^~
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:76:60: error:
'struct pwm_device' has no member named 'period'
  error = pwm_config(haptic->pwm_dev, delta, haptic->pwm_dev->period);
                                                            ^~
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c: In function
'max77693_haptic_play_effect':
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:248:41: error:
'struct pwm_device' has no member named 'period'
  period_mag_multi = (u64)haptic->pwm_dev->period * haptic->magnitude;

which are due to API change introduced by
rk3399-pwm-0008-pwm-Introduce-the-pwm_state-concept.patch (in upstream kernel
0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch is before than
rk3399-pwm-0008-pwm-Introduce-the-pwm_state-concept.patch). Since nobody found
that, I suppose this is also armv7-specific.

0007-ACPI-bus-add-stub-acpi_evaluate_dsm-to-linux-acpi.h.patch
0008-ACPI-bus-add-stub-acpi_dev_found-to-linux-acpi.h.patch

These are required to fix:

/home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c: In
function 'hns_dsaf_get_cfg':
/home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c:64:7:
error: implicit declaration of function 'acpi_dev_found'
[-Werror=implicit-function-declaration]
   if (acpi_dev_found(hns_dsaf_acpi_match[0].id))

So, actually it is SUSE kernel patch net-hns-dsaf-adds-support-of-acpi.patch
which breaks hisilicon compilation for armv7l.
I think there could be three options 1) accepting ACPI-* patches 2) fixing
net-hns-dsaf-adds-support-of-acpi.patch,
net-hns-net-hns-enet-adds-support-of-acpi.patch,
net-hns-Add-ACPI-support-to-check-SFP-present.patch and
net-hns-implement-the-miscellaneous-operation-by-asl.patch in order no to use
acpi_dev_found() and acpi_evaluate_dsm() functions at armv7l 3) disable
NET_VENDOR_HISILICON_HNS in config and not to build this code.
What would you prefer?


To be continued...