Commit cf5787f2a4f1af71e72f4faaee32685c8f82a3dd

Authored by Kumar Gala
Committed by Anatolij Gustschin
1 parent 5bfa78db4f
Exists in master and in 57 other branches 8qm-imx_v2020.04_5.4.70_2.3.0, emb_lf-6.6.52-2.2.0, emb_lf_v2022.04, emb_lf_v2023.04, emb_lf_v2024.04, imx_v2015.04_4.1.15_1.0.0_ga, pitx_8mp_lf_v2020.04, smarc-8m-android-10.0.0_2.6.0, smarc-8m-android-11.0.0_2.0.0, smarc-8mp-android-11.0.0_2.0.0, smarc-emmc-imx_v2014.04_3.10.53_1.1.0_ga, smarc-emmc-imx_v2014.04_3.14.28_1.0.0_ga, smarc-imx-l5.0.0_1.0.0-ga, smarc-imx6_v2018.03_4.14.98_2.0.0_ga, smarc-imx7_v2017.03_4.9.11_1.0.0_ga, smarc-imx7_v2018.03_4.14.98_2.0.0_ga, smarc-imx_v2014.04_3.14.28_1.0.0_ga, smarc-imx_v2015.04_4.1.15_1.0.0_ga, smarc-imx_v2017.03_4.9.11_1.0.0_ga, smarc-imx_v2017.03_4.9.88_2.0.0_ga, smarc-imx_v2017.03_o8.1.0_1.3.0_8m, smarc-imx_v2018.03_4.14.78_1.0.0_ga, smarc-m6.0.1_2.1.0-ga, smarc-n7.1.2_2.0.0-ga, smarc-rel_imx_4.1.15_2.0.0_ga, smarc_8m-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8m-imx_v2019.04_4.19.35_1.1.0, smarc_8m_00d0-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2019.04_4.19.35_1.1.0, smarc_8mm-imx_v2020.04_5.4.24_2.1.0, smarc_8mp_lf_v2020.04, smarc_8mq-imx_v2020.04_5.4.24_2.1.0, smarc_8mq_lf_v2020.04, ti-u-boot-2015.07, u-boot-2013.01.y, v2013.10, v2013.10-smarct33, v2013.10-smartmen, v2014.01, v2014.04, v2014.04-smarct33, v2014.04-smarct33-emmc, v2014.04-smartmen, v2014.07, v2014.07-smarct33, v2014.07-smartmen, v2015.07-smarct33, v2015.07-smarct33-emmc, v2015.07-smarct4x, v2016.05-dlt, v2016.05-smarct3x, v2016.05-smarct3x-emmc, v2016.05-smarct4x, v2017.01-smarct3x, v2017.01-smarct3x-emmc, v2017.01-smarct4x

pci: fix some warnings related to assumptions about

The following commit introduced some warnings associated with using
pci_addr_t instead of a proper 32-bit data type.

commit af778c6d9e2b945ee03cbc53bb976238a3374f33
Author: Andrew Sharp <andywyse6@gmail.com>
Date:   Wed Aug 1 12:27:16 2012 +0000

    pci: fix errant data types and corresponding access functions

On some platforms pci_addr_t is defined as a 64-bit data type so its not
proper to use with pci_{read,write}_config_dword.

Signed-off-by: Kumar Gala <galak@kernel.crashing.org>

Showing 2 changed files with 4 additions and 4 deletions Side-by-side Diff

... ... @@ -118,11 +118,11 @@
118 118 void *pci_map_bar(pci_dev_t pdev, int bar, int flags)
119 119 {
120 120 pci_addr_t pci_bus_addr;
121   - pci_addr_t bar_response;
  121 + u32 bar_response;
122 122  
123 123 /* read BAR address */
124 124 pci_read_config_dword(pdev, bar, &bar_response);
125   - pci_bus_addr = bar_response & ~0xf;
  125 + pci_bus_addr = (pci_addr_t)(bar_response & ~0xf);
126 126  
127 127 /*
128 128 * Pass "0" as the length argument to pci_bus_to_virt. The arg
... ... @@ -389,7 +389,7 @@
389 389 pci_addr_t mem,
390 390 unsigned long command)
391 391 {
392   - pci_addr_t bar_response;
  392 + u32 bar_response;
393 393 unsigned int old_command;
394 394 pci_addr_t bar_value;
395 395 pci_size_t bar_size;
drivers/pci/pci_auto.c
... ... @@ -89,7 +89,7 @@
89 89 struct pci_region *prefetch,
90 90 struct pci_region *io)
91 91 {
92   - pci_addr_t bar_response;
  92 + u32 bar_response;
93 93 pci_size_t bar_size;
94 94 u16 cmdstat = 0;
95 95 int bar, bar_nr = 0;