tree 146361e9bfc3cc1b7b463794f0a608b7ec5ffbac
parent eefb5f3ab2e8e0b3ef5eba5c5a9f33457741300d
author Atish Patra <atish.patra@wdc.com> 1611946838 -0800
committer Palmer Dabbelt <palmerdabbelt@google.com> 1612319802 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQJHBAABCgAxFiEEKzw3R0RoQ7JKlDp6LhMZ81+7GIkFAmAaDEsTHHBhbG1lckBk
 YWJiZWx0LmNvbQAKCRAuExnzX7sYicItD/4kCgerFqLnaA5g21y+4jrrJrXPA2bB
 dGyTp5fMJdHek3A6J9zAudm04aSjPImPemEqZUin/ERCLPIcVl1p1dDvqRKK+5e7
 ByW036EJJIE1HTOWjH/Hip7feNANtpjEVh2cIkGPeemMYFesOBGJQYV7+DWSAL2f
 1hHG34d2C/pl9pGHo0fU7U2Dq8R8qb95mDquXUTbFl/HChDoyMAkpcS81NQhzMsp
 YeTm17wKNvf1Lz2qLdU8nTJHBgmAqtbOvGMMgwYETB+iuomKk0d4H2ssKbU+zq/i
 Ln/vjb0ItZeofUAEDdaE3LbffEqiDRhbk9mrGU39FA1T5Np/kIeCLVQRKO7p4oqF
 SZI2eLq6w029W7THEDVLjFxuaigLlqeq/yr1VmA/jd3jmu1Nt4lxSc5PgZbI2ina
 GFozNkva41RvnznqEnmD9Quszj5RgkR7CCORbQKSuBrYuIWJfQZD85Gs+84KOQJp
 q4XCi68VzF+vBkdyBCpNQ4GVG+NcQ+/SLhW7GSYTIHvvDDyaWipsLBScOmQv0C1Y
 +PvAXF1KDUpkRHkzKvB1vmuhEa7YtRlHbAYoI4M2GNXXHBq+6rjYQyKRYY7eiIaQ
 ru0FiOiECoa9WrexUET6C7olxSX7ousIXXTWkJKlaWmJGutveBOZPjivKYK+io7F
 eNdbS3dCjBfD6A==
 =YenW
 -----END PGP SIGNATURE-----

RISC-V: Define MAXPHYSMEM_1GB only for RV32

MAXPHYSMEM_1GB option was added for RV32 because RV32 only supports 1GB
of maximum physical memory. This lead to few compilation errors reported
by kernel test robot which created the following configuration combination
which are not useful but can be configured.

1. MAXPHYSMEM_1GB & RV64
2, MAXPHYSMEM_2GB & RV32

Fix this by restricting MAXPHYSMEM_1GB for RV32 and MAXPHYSMEM_2GB only for
RV64.

Fixes: e557793799c5 ("RISC-V: Fix maximum allowed phsyical memory for RV32")
Cc: stable@vger.kernel.org
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Atish Patra <atish.patra@wdc.com>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>