Re: [PATCH] bus: omap_l3_noc: Fix master id address decoding for OMAP5

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

 




On Fri, Apr 24, 2015 at 2:10 PM, Suman Anna <s-anna@xxxxxx> wrote:
> On 04/24/2015 01:33 PM, Nishanth Menon wrote:
>> On 04/24/2015 12:54 PM, Suman Anna wrote:

...
>>> -static struct l3_target_data omap_l3_target_data_clk3[] = {
>>> -    {0x0100, "EMUSS",},
>>> -    {0x0300, "DEBUG SOURCE",},
>>> -    {0x0,   "HOST CLK3",},
^^ this was HOST CLK3


..
>>>
>>> +/* OMAP5 data */
>>> +static struct l3_target_data omap5_l3_target_data_clk3[] = {
>>> +    {0x0100, "L3INSTR",},
>>> +    {0x0300, "DEBUGSS",},
>>> +    {0x0,    "HOSTCLK3",},
>>
>> "HOST CLK"
>
> Why? I followed the convention used for the other two HOST CLKs for the

so asked, if it should be HOST<space>CLK3
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[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