* [RFC] PCI: dwc: designware: allow customize unroll registers' readl/writel
@ 2017-07-13 10:48 Jisheng Zhang
2017-07-13 10:52 ` Jisheng Zhang
0 siblings, 1 reply; 3+ messages in thread
From: Jisheng Zhang @ 2017-07-13 10:48 UTC (permalink / raw)
To: linux-arm-kernel
Hi Joao, Jingoo,
Now, the PCIE_GET_ATU_OUTB_UNR_REG_OFFSET macro is defined as:
/* Register address builder */
#define PCIE_GET_ATU_OUTB_UNR_REG_OFFSET(region) \
((0x3 << 20) | ((region) << 9))
I have one question: where does the (0x3 << 20) come from? 2MB space, a bit
large. And I didn't find it in the databook. Is it platform specific?
If yes, I want to cook one patch to customize unroll registers' readl/writel.
And how does (0x3 << 20) enable DBI2 access?
Thanks in advance,
Jisheng
^ permalink raw reply [flat|nested] 3+ messages in thread
* [RFC] PCI: dwc: designware: allow customize unroll registers' readl/writel
2017-07-13 10:48 [RFC] PCI: dwc: designware: allow customize unroll registers' readl/writel Jisheng Zhang
@ 2017-07-13 10:52 ` Jisheng Zhang
2017-07-17 8:59 ` Joao Pinto
0 siblings, 1 reply; 3+ messages in thread
From: Jisheng Zhang @ 2017-07-13 10:52 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, 13 Jul 2017 18:48:37 +0800 Jisheng Zhang wrote:
> Hi Joao, Jingoo,
>
> Now, the PCIE_GET_ATU_OUTB_UNR_REG_OFFSET macro is defined as:
>
> /* Register address builder */
> #define PCIE_GET_ATU_OUTB_UNR_REG_OFFSET(region) \
> ((0x3 << 20) | ((region) << 9))
>
> I have one question: where does the (0x3 << 20) come from? 2MB space, a bit
sorry, typo. (0x3 << 20) should be 3MB.
> large. And I didn't find it in the databook. Is it platform specific?
> If yes, I want to cook one patch to customize unroll registers' readl/writel.
>
> And how does (0x3 << 20) enable DBI2 access?
>
> Thanks in advance,
> Jisheng
^ permalink raw reply [flat|nested] 3+ messages in thread
* [RFC] PCI: dwc: designware: allow customize unroll registers' readl/writel
2017-07-13 10:52 ` Jisheng Zhang
@ 2017-07-17 8:59 ` Joao Pinto
0 siblings, 0 replies; 3+ messages in thread
From: Joao Pinto @ 2017-07-17 8:59 UTC (permalink / raw)
To: linux-arm-kernel
Hi Jisheng,
?s 11:52 AM de 7/13/2017, Jisheng Zhang escreveu:
> On Thu, 13 Jul 2017 18:48:37 +0800 Jisheng Zhang wrote:
>
>> Hi Joao, Jingoo,
>>
>> Now, the PCIE_GET_ATU_OUTB_UNR_REG_OFFSET macro is defined as:
>>
>> /* Register address builder */
>> #define PCIE_GET_ATU_OUTB_UNR_REG_OFFSET(region) \
>> ((0x3 << 20) | ((region) << 9))
>>
>> I have one question: where does the (0x3 << 20) come from? 2MB space, a bit
From, the PCIe Core 4.80 you have the new feature Unroll, which was developed
for both iATU and DMA.
To inform the Core that you want to access an Unroll register address, bits 20
and 21 must be set, and thats where 0x3 comes from.
If it is not clear please let me know.
>
> sorry, typo. (0x3 << 20) should be 3MB.
>
>> large. And I didn't find it in the databook. Is it platform specific?
>> If yes, I want to cook one patch to customize unroll registers' readl/writel.
>>
>> And how does (0x3 << 20) enable DBI2 access?
>>
>> Thanks in advance,
>> Jisheng
>
Thanks,
Joao
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-17 8:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-07-13 10:48 [RFC] PCI: dwc: designware: allow customize unroll registers' readl/writel Jisheng Zhang
2017-07-13 10:52 ` Jisheng Zhang
2017-07-17 8:59 ` Joao Pinto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).