Ravi,
On 27/07/2023 08:36, Ravi Gunasekaran wrote:
>
>
> On 7/26/23 6:22 PM, Nishanth Menon wrote:
>> On 14:44-20230726, Ravi Gunasekaran wrote:
>> [...]
>>> If it is the former, then would a duplicate mdio node help keep the changes
>>> to minimum?
>>
>> That is worse hack. How does it make
On 7/26/23 6:22 PM, Nishanth Menon wrote:
> On 14:44-20230726, Ravi Gunasekaran wrote:
> [...]
>> If it is the former, then would a duplicate mdio node help keep the changes
>> to minimum?
>
> That is worse hack. How does it make sense to have two mdio nodes to
> represent the same hardware
Maxime,
On 7/26/23 6:19 PM, Maxime Ripard wrote:
> Hi Ravi,
>
> On Wed, Jul 26, 2023 at 02:44:00PM +0530, Ravi Gunasekaran wrote:
>> On 7/20/23 7:42 PM, Maxime Ripard wrote:
>>> Hi
>>>
>>> Sorry, I didn't receive Roger mail so I'll reply here
>>>
>>> On Thu, Jul 20, 2023 at 09:00:19AM -0500,
Maxime,
On 7/20/23 7:42 PM, Maxime Ripard wrote:
> Hi
>
> Sorry, I didn't receive Roger mail so I'll reply here
>
> On Thu, Jul 20, 2023 at 09:00:19AM -0500, Nishanth Menon wrote:
>> On 16:56-20230720, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 20/07/2023 16:33, Ravi Gunasekaran wrote:
Hi Ravi,
On Wed, Jul 26, 2023 at 02:44:00PM +0530, Ravi Gunasekaran wrote:
> On 7/20/23 7:42 PM, Maxime Ripard wrote:
> > Hi
> >
> > Sorry, I didn't receive Roger mail so I'll reply here
> >
> > On Thu, Jul 20, 2023 at 09:00:19AM -0500, Nishanth Menon wrote:
> >> On 16:56-20230720, Roger
On 14:44-20230726, Ravi Gunasekaran wrote:
[...]
> If it is the former, then would a duplicate mdio node help keep the changes
> to minimum?
That is worse hack. How does it make sense to have two mdio nodes to
represent the same hardware block? we are trying to get closer to kernel
dts support
On 17:41-20230720, Roger Quadros wrote:
[...]
> >> from what I understand, is around 2024 timeframe.. which is probably not
> >> something that helps us in the community at this point.
>
> OK, then we need to resort to some temporary solution like this then.
Thanks. I will squash up the fixup
On 20/07/2023 17:12, Maxime Ripard wrote:
> Hi
>
> Sorry, I didn't receive Roger mail so I'll reply here
>
> On Thu, Jul 20, 2023 at 09:00:19AM -0500, Nishanth Menon wrote:
>> On 16:56-20230720, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 20/07/2023 16:33, Ravi Gunasekaran wrote:
Hi
Sorry, I didn't receive Roger mail so I'll reply here
On Thu, Jul 20, 2023 at 09:00:19AM -0500, Nishanth Menon wrote:
> On 16:56-20230720, Roger Quadros wrote:
> > Hi,
> >
> > On 20/07/2023 16:33, Ravi Gunasekaran wrote:
> > >
> > >
> > > On 7/20/2023 3:25 PM, Maxime Ripard wrote:
> > >>
Hi,
This series is based on:
https://lore.kernel.org/all/20230713072019.3153871-1...@ti.com/
It fixes the issue of Linux booting from the DT embedded by U-boot. The
main issue there is that U-Boot doesn't handle the MDIO child node that
might have resources attached to it.
Thus, any pinctrl
On 16:56-20230720, Roger Quadros wrote:
> Hi,
>
> On 20/07/2023 16:33, Ravi Gunasekaran wrote:
> >
> >
> > On 7/20/2023 3:25 PM, Maxime Ripard wrote:
> >> Hi,
> >>
> >> This series is based on:
> >> https://lore.kernel.org/all/20230713072019.3153871-1...@ti.com/
> >>
> >> It fixes the issue of
Hi,
On 20/07/2023 16:33, Ravi Gunasekaran wrote:
>
>
> On 7/20/2023 3:25 PM, Maxime Ripard wrote:
>> Hi,
>>
>> This series is based on:
>> https://lore.kernel.org/all/20230713072019.3153871-1...@ti.com/
>>
>> It fixes the issue of Linux booting from the DT embedded by U-boot. The
>> main issue
On 7/20/2023 3:25 PM, Maxime Ripard wrote:
> Hi,
>
> This series is based on:
> https://lore.kernel.org/all/20230713072019.3153871-1...@ti.com/
>
> It fixes the issue of Linux booting from the DT embedded by U-boot. The
> main issue there is that U-Boot doesn't handle the MDIO child node that
>
13 matches
Mail list logo
