Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Chen-Yu Tsai
On Fri, Aug 18, 2017 at 2:23 PM, Icenowy Zheng wrote: > > > 于 2017年8月18日 GMT+08:00 下午2:21:07, Chen-Yu Tsai 写到: >>Hi, >> >>On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: >>> When claiming SRAM, if the base is set to an error, it means that

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Chen-Yu Tsai
On Fri, Aug 18, 2017 at 2:23 PM, Icenowy Zheng wrote: > > > 于 2017年8月18日 GMT+08:00 下午2:21:07, Chen-Yu Tsai 写到: >>Hi, >> >>On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: >>> When claiming SRAM, if the base is set to an error, it means that the >>> SRAM controller has been probed, but

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Icenowy Zheng
于 2017年8月18日 GMT+08:00 下午2:21:07, Chen-Yu Tsai 写到: >Hi, > >On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: >> When claiming SRAM, if the base is set to an error, it means that the >> SRAM controller has been probed, but failed to remap the controller >>

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Icenowy Zheng
于 2017年8月18日 GMT+08:00 下午2:21:07, Chen-Yu Tsai 写到: >Hi, > >On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: >> When claiming SRAM, if the base is set to an error, it means that the >> SRAM controller has been probed, but failed to remap the controller >> memory zone. If the base is zero,

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Chen-Yu Tsai
Hi, On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: > When claiming SRAM, if the base is set to an error, it means that the > SRAM controller has been probed, but failed to remap the controller > memory zone. If the base is zero, thus the SRAM controller should be not >

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-18 Thread Chen-Yu Tsai
Hi, On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: > When claiming SRAM, if the base is set to an error, it means that the > SRAM controller has been probed, but failed to remap the controller > memory zone. If the base is zero, thus the SRAM controller should be not > probed at all, and

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-09 Thread Chen-Yu Tsai
On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: > When claiming SRAM, if the base is set to an error, it means that the > SRAM controller has been probed, but failed to remap the controller > memory zone. If the base is zero, thus the SRAM controller should be not > probed

Re: [linux-sunxi] [PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-09 Thread Chen-Yu Tsai
On Wed, Aug 9, 2017 at 4:56 PM, Icenowy Zheng wrote: > When claiming SRAM, if the base is set to an error, it means that the > SRAM controller has been probed, but failed to remap the controller > memory zone. If the base is zero, thus the SRAM controller should be not > probed at all, and it

[PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-09 Thread Icenowy Zheng
When claiming SRAM, if the base is set to an error, it means that the SRAM controller has been probed, but failed to remap the controller memory zone. If the base is zero, thus the SRAM controller should be not probed at all, and it should return -EPROBE_DEFER. However, currently we returned

[PATCH 2/4] drivers: soc: sunxi: fix error processing on base address when claiming

2017-08-09 Thread Icenowy Zheng
When claiming SRAM, if the base is set to an error, it means that the SRAM controller has been probed, but failed to remap the controller memory zone. If the base is zero, thus the SRAM controller should be not probed at all, and it should return -EPROBE_DEFER. However, currently we returned