Hi Raghavendra,
I have not received your emails in this conversation, and I do not see
them in my spam folder. I see some replies from Rob, so I am guessing
he added me to the CC: list.
Please add me to future Devicetree emails.
Digging a little deeper, in the devicetree mail list archive, I se
On Wed, Sep 18, 2019 at 03:32:14PM -0700, rana...@codeaurora.org wrote:
> On 2019-09-18 13:13, Rob Herring wrote:
> > On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
> > wrote:
> > >
> > > On some embedded systems, the '/memory' dt-property gets updated
> > > by the bootloader (for example
On 2019-09-18 13:13, Rob Herring wrote:
On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
wrote:
On some embedded systems, the '/memory' dt-property gets updated
by the bootloader (for example, the DDR configuration) and then
gets passed onto the kernel. The device drivers may have to rea
On Wed, Sep 18, 2019 at 1:47 PM Raghavendra Rao Ananta
wrote:
>
> On some embedded systems, the '/memory' dt-property gets updated
> by the bootloader (for example, the DDR configuration) and then
> gets passed onto the kernel. The device drivers may have to read
> the properties at runtime to mak
On some embedded systems, the '/memory' dt-property gets updated
by the bootloader (for example, the DDR configuration) and then
gets passed onto the kernel. The device drivers may have to read
the properties at runtime to make decisions. Hence, add
of_get_memory_prop() for the device drivers to qu
5 matches
Mail list logo