* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-09 12:27 ` Inochi Amaoto
0 siblings, 0 replies; 26+ messages in thread
From: Inochi Amaoto @ 2024-04-09 12:27 UTC (permalink / raw)
To: Conor Dooley, Inochi Amaoto
Cc: michael.opdenacker, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou,
devicetree, linux-riscv, linux-kernel
On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > >
> > > This adds initial support for the Milk-V Duo S board
> > > (https://milkv.io/duo-s), enabling the serial port and
> > > read-only SD card support, allowing to boot Linux to the
> > > command line.
> > >
> >
> > Hi Michael,
> >
> > I think your patch losts the board binding and have wrong compatiable.
> > Also, the SD can have rw support with proper property. See link [1]
> > (need 'disable-wp').
>
> [1] doesn't go anywhere useful.
>
This is my fault, I copied the wrong url. The right patch is
https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
> > I suggest you resubmitting this patch after applying clk patchs.
> > This could reduce some unnecessary change. For now, you can just
> > use the dts for huashan-pi (with changed memory size).
>
> Why would using patched huashan-pi dts be more suitable than carrying
> a local patch for duo-s devicetree? What am I missing?
>
> Cheers,
> Conor.
>
> >
> > [1]: https://lore.kernel.org/linux-riscv/IA1PR20MB4953B158F6F575840F3D4267BB7D2@IA1PR20MB4953.namprd20.prod.outlook.com/
I think you miss nothing. Using huashan-pi dts as a temporary
solution is just because they are both CV181X series. Since
only a few peripherals are supported, it is also OK to use duo
dts with local change. They're not significantly different.
This is also the reason I did not prepare any patch for the
new board. (such as lichee RV NANO, duo 256).
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-09 12:27 ` Inochi Amaoto
@ 2024-04-09 12:30 ` Inochi Amaoto
-1 siblings, 0 replies; 26+ messages in thread
From: Inochi Amaoto @ 2024-04-09 12:30 UTC (permalink / raw)
To: michael.opdenacker, Inochi Amaoto
Cc: Conor Dooley, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou, devicetree,
linux-riscv, linux-kernel
On Tue, Apr 09, 2024 at 08:27:59PM +0800, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > >
> > > > This adds initial support for the Milk-V Duo S board
> > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > read-only SD card support, allowing to boot Linux to the
> > > > command line.
> > > >
> > >
> > > Hi Michael,
> > >
> > > I think your patch losts the board binding and have wrong compatiable.
> > > Also, the SD can have rw support with proper property. See link [1]
> > > (need 'disable-wp').
> >
> > [1] doesn't go anywhere useful.
> >
>
> This is my fault, I copied the wrong url. The right patch is
> https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
>
FYI, Michael. This is the right url for sdhci dts. The previous
is wrong.
> > > I suggest you resubmitting this patch after applying clk patchs.
> > > This could reduce some unnecessary change. For now, you can just
> > > use the dts for huashan-pi (with changed memory size).
> >
> > Why would using patched huashan-pi dts be more suitable than carrying
> > a local patch for duo-s devicetree? What am I missing?
> >
> > Cheers,
> > Conor.
> >
> > >
> > > [1]: https://lore.kernel.org/linux-riscv/IA1PR20MB4953B158F6F575840F3D4267BB7D2@IA1PR20MB4953.namprd20.prod.outlook.com/
>
> I think you miss nothing. Using huashan-pi dts as a temporary
> solution is just because they are both CV181X series. Since
> only a few peripherals are supported, it is also OK to use duo
> dts with local change. They're not significantly different.
> This is also the reason I did not prepare any patch for the
> new board. (such as lichee RV NANO, duo 256).
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-09 12:30 ` Inochi Amaoto
0 siblings, 0 replies; 26+ messages in thread
From: Inochi Amaoto @ 2024-04-09 12:30 UTC (permalink / raw)
To: michael.opdenacker, Inochi Amaoto
Cc: Conor Dooley, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou, devicetree,
linux-riscv, linux-kernel
On Tue, Apr 09, 2024 at 08:27:59PM +0800, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > >
> > > > This adds initial support for the Milk-V Duo S board
> > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > read-only SD card support, allowing to boot Linux to the
> > > > command line.
> > > >
> > >
> > > Hi Michael,
> > >
> > > I think your patch losts the board binding and have wrong compatiable.
> > > Also, the SD can have rw support with proper property. See link [1]
> > > (need 'disable-wp').
> >
> > [1] doesn't go anywhere useful.
> >
>
> This is my fault, I copied the wrong url. The right patch is
> https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
>
FYI, Michael. This is the right url for sdhci dts. The previous
is wrong.
> > > I suggest you resubmitting this patch after applying clk patchs.
> > > This could reduce some unnecessary change. For now, you can just
> > > use the dts for huashan-pi (with changed memory size).
> >
> > Why would using patched huashan-pi dts be more suitable than carrying
> > a local patch for duo-s devicetree? What am I missing?
> >
> > Cheers,
> > Conor.
> >
> > >
> > > [1]: https://lore.kernel.org/linux-riscv/IA1PR20MB4953B158F6F575840F3D4267BB7D2@IA1PR20MB4953.namprd20.prod.outlook.com/
>
> I think you miss nothing. Using huashan-pi dts as a temporary
> solution is just because they are both CV181X series. Since
> only a few peripherals are supported, it is also OK to use duo
> dts with local change. They're not significantly different.
> This is also the reason I did not prepare any patch for the
> new board. (such as lichee RV NANO, duo 256).
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-09 12:27 ` Inochi Amaoto
@ 2024-04-09 13:08 ` Michael Opdenacker
-1 siblings, 0 replies; 26+ messages in thread
From: Michael Opdenacker @ 2024-04-09 13:08 UTC (permalink / raw)
To: Inochi Amaoto, Conor Dooley
Cc: michael.opdenacker, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou,
devicetree, linux-riscv, linux-kernel
Hi Inochi
On 4/9/24 at 14:27, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
>> On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
>>> On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
>>>> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>>>>
>>>> This adds initial support for the Milk-V Duo S board
>>>> (https://milkv.io/duo-s), enabling the serial port and
>>>> read-only SD card support, allowing to boot Linux to the
>>>> command line.
>>>>
>>> Hi Michael,
>>>
>>> I think your patch losts the board binding and have wrong compatiable.
>>> Also, the SD can have rw support with proper property. See link [1]
>>> (need 'disable-wp').
>> [1] doesn't go anywhere useful.
>>
> This is my fault, I copied the wrong url. The right patch is
> https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
No problem, I found out.
I confirm that using the "disable-wp;" property does the trick to make
the MMC writable.
However, it wasn't mentioned in the above URL...
By the way, do I really need those under &sdhci0?
+ bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
My board looks happy so far without them ;-)
Thanks again for your help
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-09 13:08 ` Michael Opdenacker
0 siblings, 0 replies; 26+ messages in thread
From: Michael Opdenacker @ 2024-04-09 13:08 UTC (permalink / raw)
To: Inochi Amaoto, Conor Dooley
Cc: michael.opdenacker, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou,
devicetree, linux-riscv, linux-kernel
Hi Inochi
On 4/9/24 at 14:27, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
>> On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
>>> On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
>>>> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>>>>
>>>> This adds initial support for the Milk-V Duo S board
>>>> (https://milkv.io/duo-s), enabling the serial port and
>>>> read-only SD card support, allowing to boot Linux to the
>>>> command line.
>>>>
>>> Hi Michael,
>>>
>>> I think your patch losts the board binding and have wrong compatiable.
>>> Also, the SD can have rw support with proper property. See link [1]
>>> (need 'disable-wp').
>> [1] doesn't go anywhere useful.
>>
> This is my fault, I copied the wrong url. The right patch is
> https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
No problem, I found out.
I confirm that using the "disable-wp;" property does the trick to make
the MMC writable.
However, it wasn't mentioned in the above URL...
By the way, do I really need those under &sdhci0?
+ bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
My board looks happy so far without them ;-)
Thanks again for your help
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-09 13:08 ` Michael Opdenacker
@ 2024-04-10 1:24 ` Inochi Amaoto
-1 siblings, 0 replies; 26+ messages in thread
From: Inochi Amaoto @ 2024-04-10 1:24 UTC (permalink / raw)
To: Jisheng Zhang
Cc: Michael Opdenacker, Inochi Amaoto, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
On Tue, Apr 09, 2024 at 03:08:17PM +0200, Michael Opdenacker wrote:
> Hi Inochi
>
> On 4/9/24 at 14:27, Inochi Amaoto wrote:
> > On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > > >
> > > > > This adds initial support for the Milk-V Duo S board
> > > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > > read-only SD card support, allowing to boot Linux to the
> > > > > command line.
> > > > >
> > > > Hi Michael,
> > > >
> > > > I think your patch losts the board binding and have wrong compatiable.
> > > > Also, the SD can have rw support with proper property. See link [1]
> > > > (need 'disable-wp').
> > > [1] doesn't go anywhere useful.
> > >
> > This is my fault, I copied the wrong url. The right patch is
> > https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
>
>
> No problem, I found out.
> I confirm that using the "disable-wp;" property does the trick to make the
> MMC writable.
>
> However, it wasn't mentioned in the above URL...
>
> By the way, do I really need those under &sdhci0?
>
> + bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
>
> My board looks happy so far without them ;-)
FYI, Jisheng. Could you share some suggestions?
> Thanks again for your help
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-10 1:24 ` Inochi Amaoto
0 siblings, 0 replies; 26+ messages in thread
From: Inochi Amaoto @ 2024-04-10 1:24 UTC (permalink / raw)
To: Jisheng Zhang
Cc: Michael Opdenacker, Inochi Amaoto, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
On Tue, Apr 09, 2024 at 03:08:17PM +0200, Michael Opdenacker wrote:
> Hi Inochi
>
> On 4/9/24 at 14:27, Inochi Amaoto wrote:
> > On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > > >
> > > > > This adds initial support for the Milk-V Duo S board
> > > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > > read-only SD card support, allowing to boot Linux to the
> > > > > command line.
> > > > >
> > > > Hi Michael,
> > > >
> > > > I think your patch losts the board binding and have wrong compatiable.
> > > > Also, the SD can have rw support with proper property. See link [1]
> > > > (need 'disable-wp').
> > > [1] doesn't go anywhere useful.
> > >
> > This is my fault, I copied the wrong url. The right patch is
> > https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
>
>
> No problem, I found out.
> I confirm that using the "disable-wp;" property does the trick to make the
> MMC writable.
>
> However, it wasn't mentioned in the above URL...
>
> By the way, do I really need those under &sdhci0?
>
> + bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
>
> My board looks happy so far without them ;-)
FYI, Jisheng. Could you share some suggestions?
> Thanks again for your help
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-10 1:24 ` Inochi Amaoto
@ 2024-04-10 10:24 ` Jisheng Zhang
-1 siblings, 0 replies; 26+ messages in thread
From: Jisheng Zhang @ 2024-04-10 10:24 UTC (permalink / raw)
To: Inochi Amaoto
Cc: Michael Opdenacker, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
On Wed, Apr 10, 2024 at 09:24:40AM +0800, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 03:08:17PM +0200, Michael Opdenacker wrote:
> > Hi Inochi
> >
> > On 4/9/24 at 14:27, Inochi Amaoto wrote:
> > > On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > > > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > > > >
> > > > > > This adds initial support for the Milk-V Duo S board
> > > > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > > > read-only SD card support, allowing to boot Linux to the
> > > > > > command line.
> > > > > >
> > > > > Hi Michael,
> > > > >
> > > > > I think your patch losts the board binding and have wrong compatiable.
> > > > > Also, the SD can have rw support with proper property. See link [1]
> > > > > (need 'disable-wp').
> > > > [1] doesn't go anywhere useful.
> > > >
> > > This is my fault, I copied the wrong url. The right patch is
> > > https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
> >
> >
> > No problem, I found out.
> > I confirm that using the "disable-wp;" property does the trick to make the
> > MMC writable.
> >
> > However, it wasn't mentioned in the above URL...
> >
> > By the way, do I really need those under &sdhci0?
> >
> > + bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
> >
> > My board looks happy so far without them ;-)
setting the correct bus-width is necessary for better performance
no-1-8-v can be removed, but it doesn't harm anything because
the board doesn't supply 1.8v
no-mmc and no-sdio to make the probe a bit quicker
>
> FYI, Jisheng. Could you share some suggestions?
>
> > Thanks again for your help
> > Cheers
> > Michael.
> >
> > --
> > Michael Opdenacker, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> >
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-10 10:24 ` Jisheng Zhang
0 siblings, 0 replies; 26+ messages in thread
From: Jisheng Zhang @ 2024-04-10 10:24 UTC (permalink / raw)
To: Inochi Amaoto
Cc: Michael Opdenacker, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
On Wed, Apr 10, 2024 at 09:24:40AM +0800, Inochi Amaoto wrote:
> On Tue, Apr 09, 2024 at 03:08:17PM +0200, Michael Opdenacker wrote:
> > Hi Inochi
> >
> > On 4/9/24 at 14:27, Inochi Amaoto wrote:
> > > On Tue, Apr 09, 2024 at 01:13:32PM +0100, Conor Dooley wrote:
> > > > On Tue, Apr 09, 2024 at 03:17:35PM +0800, Inochi Amaoto wrote:
> > > > > On Tue, Apr 09, 2024 at 08:45:04AM +0200, michael.opdenacker@bootlin.com wrote:
> > > > > > From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> > > > > >
> > > > > > This adds initial support for the Milk-V Duo S board
> > > > > > (https://milkv.io/duo-s), enabling the serial port and
> > > > > > read-only SD card support, allowing to boot Linux to the
> > > > > > command line.
> > > > > >
> > > > > Hi Michael,
> > > > >
> > > > > I think your patch losts the board binding and have wrong compatiable.
> > > > > Also, the SD can have rw support with proper property. See link [1]
> > > > > (need 'disable-wp').
> > > > [1] doesn't go anywhere useful.
> > > >
> > > This is my fault, I copied the wrong url. The right patch is
> > > https://lore.kernel.org/r/20240217144826.3944-1-jszhang@kernel.org.
> >
> >
> > No problem, I found out.
> > I confirm that using the "disable-wp;" property does the trick to make the
> > MMC writable.
> >
> > However, it wasn't mentioned in the above URL...
> >
> > By the way, do I really need those under &sdhci0?
> >
> > + bus-width = <4>; + no-1-8-v; + no-mmc; + no-sdio;
> >
> > My board looks happy so far without them ;-)
setting the correct bus-width is necessary for better performance
no-1-8-v can be removed, but it doesn't harm anything because
the board doesn't supply 1.8v
no-mmc and no-sdio to make the probe a bit quicker
>
> FYI, Jisheng. Could you share some suggestions?
>
> > Thanks again for your help
> > Cheers
> > Michael.
> >
> > --
> > Michael Opdenacker, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> >
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-10 10:24 ` Jisheng Zhang
@ 2024-04-11 8:35 ` Michael Opdenacker
-1 siblings, 0 replies; 26+ messages in thread
From: Michael Opdenacker @ 2024-04-11 8:35 UTC (permalink / raw)
To: Jisheng Zhang, Inochi Amaoto
Cc: michael.opdenacker, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
Hi Jisheng,
On 4/10/24 at 12:24, Jisheng Zhang wrote:
> setting the correct bus-width is necessary for better performance
> no-1-8-v can be removed, but it doesn't harm anything because
> the board doesn't supply 1.8v
>
> no-mmc and no-sdio to make the probe a bit quicker
Many thanks for your advice!
However, whether I apply these changes or not,
git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git is now broken
for me:
Error: arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts:32.1-8 Label or
path sdhci0 not found
I was previously testing with linux-next, but it's now broken too,
though in a different way:
[ 1.306811] /dev/root: Can't open blockdev
[ 1.311200] VFS: Cannot open root device "/dev/mmcblk0p2" or
unknown-block(0,0): error -6
Shall I submit my updates anyway?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-11 8:35 ` Michael Opdenacker
0 siblings, 0 replies; 26+ messages in thread
From: Michael Opdenacker @ 2024-04-11 8:35 UTC (permalink / raw)
To: Jisheng Zhang, Inochi Amaoto
Cc: michael.opdenacker, Conor Dooley, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Chen Wang, Paul Walmsley,
Palmer Dabbelt, Albert Ou, devicetree, linux-riscv, linux-kernel
Hi Jisheng,
On 4/10/24 at 12:24, Jisheng Zhang wrote:
> setting the correct bus-width is necessary for better performance
> no-1-8-v can be removed, but it doesn't harm anything because
> the board doesn't supply 1.8v
>
> no-mmc and no-sdio to make the probe a bit quicker
Many thanks for your advice!
However, whether I apply these changes or not,
git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git is now broken
for me:
Error: arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts:32.1-8 Label or
path sdhci0 not found
I was previously testing with linux-next, but it's now broken too,
though in a different way:
[ 1.306811] /dev/root: Can't open blockdev
[ 1.311200] VFS: Cannot open root device "/dev/mmcblk0p2" or
unknown-block(0,0): error -6
Shall I submit my updates anyway?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
2024-04-11 8:35 ` Michael Opdenacker
@ 2024-04-11 16:14 ` Conor Dooley
-1 siblings, 0 replies; 26+ messages in thread
From: Conor Dooley @ 2024-04-11 16:14 UTC (permalink / raw)
To: Michael Opdenacker
Cc: Jisheng Zhang, Inochi Amaoto, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou,
devicetree, linux-riscv, linux-kernel
[-- Attachment #1.1: Type: text/plain, Size: 1365 bytes --]
On Thu, Apr 11, 2024 at 10:35:55AM +0200, Michael Opdenacker wrote:
> Hi Jisheng,
>
> On 4/10/24 at 12:24, Jisheng Zhang wrote:
> > setting the correct bus-width is necessary for better performance
> > no-1-8-v can be removed, but it doesn't harm anything because
> > the board doesn't supply 1.8v
> >
> > no-mmc and no-sdio to make the probe a bit quicker
>
> Many thanks for your advice!
>
> However, whether I apply these changes or not,
> git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git is now broken for
> me:
> Error: arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts:32.1-8 Label or path
> sdhci0 not found
This is probably just because you need to use the for-next branch of
https://github.com/sophgo/linux.git as your base. Palmer doesn't apply
dts patchs to the riscv repo. Usually working on linux-next is fine for
these kinds of activities.
> I was previously testing with linux-next, but it's now broken too, though in
> a different way:
> [ 1.306811] /dev/root: Can't open blockdev
> [ 1.311200] VFS: Cannot open root device "/dev/mmcblk0p2" or
> unknown-block(0,0): error -6
>
> Shall I submit my updates anyway?
This is probably worth investigating by someone, providing a longer log
would help if you don't wanna do so yourself. Did you rebase on a more
recent linux-next and this cropped up?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
@ 2024-04-11 16:14 ` Conor Dooley
0 siblings, 0 replies; 26+ messages in thread
From: Conor Dooley @ 2024-04-11 16:14 UTC (permalink / raw)
To: Michael Opdenacker
Cc: Jisheng Zhang, Inochi Amaoto, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Chen Wang, Paul Walmsley, Palmer Dabbelt, Albert Ou,
devicetree, linux-riscv, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Thu, Apr 11, 2024 at 10:35:55AM +0200, Michael Opdenacker wrote:
> Hi Jisheng,
>
> On 4/10/24 at 12:24, Jisheng Zhang wrote:
> > setting the correct bus-width is necessary for better performance
> > no-1-8-v can be removed, but it doesn't harm anything because
> > the board doesn't supply 1.8v
> >
> > no-mmc and no-sdio to make the probe a bit quicker
>
> Many thanks for your advice!
>
> However, whether I apply these changes or not,
> git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git is now broken for
> me:
> Error: arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts:32.1-8 Label or path
> sdhci0 not found
This is probably just because you need to use the for-next branch of
https://github.com/sophgo/linux.git as your base. Palmer doesn't apply
dts patchs to the riscv repo. Usually working on linux-next is fine for
these kinds of activities.
> I was previously testing with linux-next, but it's now broken too, though in
> a different way:
> [ 1.306811] /dev/root: Can't open blockdev
> [ 1.311200] VFS: Cannot open root device "/dev/mmcblk0p2" or
> unknown-block(0,0): error -6
>
> Shall I submit my updates anyway?
This is probably worth investigating by someone, providing a longer log
would help if you don't wanna do so yourself. Did you rebase on a more
recent linux-next and this cropped up?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread