Re: [PATCH 1/8] dt-bindings: memory: tegra: Add Tegra210 EMC bindings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/3/19 12:26 PM, Rob Herring wrote:
On Mon, Apr 1, 2019 at 2:58 AM Joseph Lo <josephl@xxxxxxxxxx> wrote:

On 3/31/19 2:41 PM, Rob Herring wrote:
On Mon, Mar 25, 2019 at 03:45:16PM +0800, Joseph Lo wrote:
Add the binding document for the external memory controller (EMC) which
communicates with external LPDDR4 devices. It includes the bindings of
the EMC node and the EMC table of different rates.

To support high rates for LPDDR4, the EMC table must be trained before
it can be used for runtime clock switching. It has been done by firmware
and merged to the table that Linux kernel uses. For backward
compatibility with the devices that had been launched on the market, like
Shield and Jetson platforms, the bindings in the EMC table should remain
the same. So the firmware can recognize them and merge the trained EMC
table for the kernel.

Hi Rob,

Thanks for reviewing.


Overall seems pretty bloated. How much of this really varies by board
vs. just being a dump of all the register values to stuff?

Most of them are register values. And by different SDRAM devices that
could be used on the same platform (use ram code to identify them), the
value could be different.


Primarily, I'm leary of getting a similar binding for every vendor's DDR
setup.

Some mostly trivial comments follow.

Really sorry about that. I understand these basic rules for DT bindings,
but the case here is that these un-reviewed bindings have been used in
the firmware on the shipped products. To support the same with the
upstream kernel and consider the firmware blob may not be updated, we
have no choice to just use the same bindings in the upstream kernel.

How can we deal with this case?

Simply, we do not accept bindings as-is. If we did, then there would
be no point in documenting and reviewing bindings. NVidia chose this
path and now gets to live with it.

Hi Rob,

Thanks for letting us know the criterion. We will follow up and continue the reviewing process of the binding. Please help us to review.

And we will fix the driver and firmware to use the reviewed bindings later. Need to settle the binding first.

Thanks,
Joseph




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux