Searched hist:d72a5abb (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/arch/m68k/coldfire/ |
H A D | intc-5272.c | ecb6bdcd Wed Aug 27 23:39:45 CDT 2014 Greg Ungerer <gerg@uclinux.org> m68knommu: fix size of address field for 5272 interrupt controller
Picked up by the 0-day buidler:
All warnings: >> arch/m68k/coldfire/intc-5272.c:46:20: warning: large integer implicitly truncated to unsigned type [-Woverflow] /*MCF_IRQ_EINT1*/ { .icr = MCFSIM_ICR1, .index = 28, .ack = 1, }, ...
The problem stems from the changes to make all ColdFire register addresses absolute, in commit d72a5abb ("make remaining ColdFire 5272 register definitions absolute"). That change did not take into account that the addresses were stored as offsets in the irqmap of the intc-5272.c code. Make the field that now stores register addresses big enough to hold addresses.
Signed-off-by: Greg Ungerer <gerg@uclinux.org> ecb6bdcd Wed Aug 27 23:39:45 CDT 2014 Greg Ungerer <gerg@uclinux.org> m68knommu: fix size of address field for 5272 interrupt controller Picked up by the 0-day buidler: All warnings: >> arch/m68k/coldfire/intc-5272.c:46:20: warning: large integer implicitly truncated to unsigned type [-Woverflow] /*MCF_IRQ_EINT1*/ { .icr = MCFSIM_ICR1, .index = 28, .ack = 1, }, ... The problem stems from the changes to make all ColdFire register addresses absolute, in commit d72a5abb ("make remaining ColdFire 5272 register definitions absolute"). That change did not take into account that the addresses were stored as offsets in the irqmap of the intc-5272.c code. Make the field that now stores register addresses big enough to hold addresses. Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|
/openbmc/linux/arch/m68k/include/asm/ |
H A D | m5272sim.h | d72a5abb Fri Sep 14 01:25:12 CDT 2012 Greg Ungerer <gerg@uclinux.org> m68knommu: make remaining ColdFire 5272 register definitions absolute addresses
Make the remaining definitions of the 5272 ColdFire registers absolute addresses. Currently some are relative to the MBAR peripheral region.
The various ColdFire parts use different methods to address the internal registers, some are absolute, some are relative to peripheral regions which can be mapped at different address ranges (such as the MBAR and IPSBAR registers). We don't want to deal with this in the code when we are accessing these registers, so make all register definitions the absolute address - factoring out whether it is an offset into a peripheral region.
This makes them all consistently defined, and reduces the occasional bugs caused by inconsistent definition of the register addresses.
Signed-off-by: Greg Ungerer <gerg@uclinux.org> d72a5abb Fri Sep 14 01:25:12 CDT 2012 Greg Ungerer <gerg@uclinux.org> m68knommu: make remaining ColdFire 5272 register definitions absolute addresses Make the remaining definitions of the 5272 ColdFire registers absolute addresses. Currently some are relative to the MBAR peripheral region. The various ColdFire parts use different methods to address the internal registers, some are absolute, some are relative to peripheral regions which can be mapped at different address ranges (such as the MBAR and IPSBAR registers). We don't want to deal with this in the code when we are accessing these registers, so make all register definitions the absolute address - factoring out whether it is an offset into a peripheral region. This makes them all consistently defined, and reduces the occasional bugs caused by inconsistent definition of the register addresses. Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|