[PATCH] poplar: add myself as co-maintainer

[PATCH] poplar: add myself as co-maintainer

[Igor Opaniuk]

Add myself as co-maintainer for Poplar board, as I'm currently
working on it (re-testing releases, addressing issues etc).

CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
CC: Shawn Guo <shawn.guo@linaro.org>
Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
---

 board/hisilicon/poplar/MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/board/hisilicon/poplar/MAINTAINERS b/board/hisilicon/poplar/MAINTAINERS
index bfd4a9be66b..01efc96b0d3 100644
--- a/board/hisilicon/poplar/MAINTAINERS
+++ b/board/hisilicon/poplar/MAINTAINERS
@@ -1,6 +1,7 @@
 Poplar BOARD
 M:     Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
 M:     Shawn Guo <shawn.guo@linaro.org>
+M:     Igor Opaniuk <igor.opaniuk@gmail.com>
 S:     Maintained
 F:     board/hisilicon/poplar
 F:     doc/board/hisilicon/poplar.rst
-- 
2.34.1

Re: [PATCH] poplar: add myself as co-maintainer

[Shawn Guo]

On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
>
> Add myself as co-maintainer for Poplar board, as I'm currently
> working on it (re-testing releases, addressing issues etc).
>
> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> CC: Shawn Guo <shawn.guo@linaro.org>
> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>

Acked-by: Shawn Guo <shawn.guo@linaro.org>

I'm not actively working on poplar any more, so maybe remove me in the meantime.

Shawn

Re: [PATCH] poplar: add myself as co-maintainer

[Jorge Ramirez-Ortiz, Gmail]

On 03/02/24 07:54:22, Shawn Guo wrote:
> On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
> >
> > Add myself as co-maintainer for Poplar board, as I'm currently
> > working on it (re-testing releases, addressing issues etc).
> >
> > CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> > CC: Shawn Guo <shawn.guo@linaro.org>
> > Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
>
> Acked-by: Shawn Guo <shawn.guo@linaro.org>
>
> I'm not actively working on poplar any more, so maybe remove me in the meantime.


hi Igor,

Yes please go ahead and thanks for offering.

I'll sync with you later next week (I found my Poplar in storage, so maybe we cam improve things a little)
Also it would be good if we knew there are still users.


Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>

>
> Shawn

Re: [PATCH] poplar: add myself as co-maintainer

[Yang Xiwen]

On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
> On 03/02/24 07:54:22, Shawn Guo wrote:
>> On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
>>>
>>> Add myself as co-maintainer for Poplar board, as I'm currently
>>> working on it (re-testing releases, addressing issues etc).
>>>
>>> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
>>> CC: Shawn Guo <shawn.guo@linaro.org>
>>> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
>>
>> Acked-by: Shawn Guo <shawn.guo@linaro.org>
>>
>> I'm not actively working on poplar any more, so maybe remove me in the meantime.
> 
> 
> hi Igor,
> 
> Yes please go ahead and thanks for offering.
> 
> I'll sync with you later next week (I found my Poplar in storage, so maybe we cam improve things a little)
> Also it would be good if we knew there are still users.
> 
> 
> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> 
Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is 
very similar to the Hi3798CV200 SoC and many peripherals and drivers can 
be reused. I think you can try moving 
arch/arm/include/asm/arch-hi3798cv200 to arch/arm/mach-histb and let's 
maintain all HiSTB series SoCs/boards under it altogether? The same 
thing also applies to TF-A. Currently upstream code refers to poplar 
everywhere but actually the port is portable enough to handle a lot of 
other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x etc..
>>
>> Shawn

Re: [PATCH] poplar: add myself as co-maintainer

[Yang Xiwen]

On 2/3/2024 5:45 PM, Yang Xiwen wrote:
> On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
>> On 03/02/24 07:54:22, Shawn Guo wrote:
>>> On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk 
>>> <igor.opaniuk@foundries.io> wrote:
>>>>
>>>> Add myself as co-maintainer for Poplar board, as I'm currently
>>>> working on it (re-testing releases, addressing issues etc).
>>>>
>>>> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
>>>> CC: Shawn Guo <shawn.guo@linaro.org>
>>>> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
>>>
>>> Acked-by: Shawn Guo <shawn.guo@linaro.org>
>>>
>>> I'm not actively working on poplar any more, so maybe remove me in 
>>> the meantime.
>>
>>
>> hi Igor,
>>
>> Yes please go ahead and thanks for offering.
>>
>> I'll sync with you later next week (I found my Poplar in storage, so 
>> maybe we cam improve things a little)
>> Also it would be good if we knew there are still users.
>>
>>
>> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
>>
> Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is 
> very similar to the Hi3798CV200 SoC and many peripherals and drivers can 
> be reused. I think you can try moving 
> arch/arm/include/asm/arch-hi3798cv200 to arch/arm/mach-histb and let's 
> maintain all HiSTB series SoCs/boards under it altogether? The same 
> thing also applies to TF-A. Currently upstream code refers to poplar 
> everywhere but actually the port is portable enough to handle a lot of 
> other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x etc..
There are some patches i sent pending for review. They are mostly 
originally sent just for Hi3798MV200, but the framework(such as 
drivers/clk/hisilicon) can be also used for poplar too. I hope you guys 
can take a look at them[1] and give your opinions about them(RBs and 
Acks are welcomed).

[1] HiSi clk framework: 
https://lore.kernel.org/u-boot/20240119-b4-hisi-clk-v1-0-279e38c95ca2@outlook.com/
>>>
>>> Shawn
> 

Re: [PATCH] poplar: add myself as co-maintainer

[Jorge Ramirez-Ortiz, Gmail]

On 03/02/24 17:45:42, Yang Xiwen wrote:
> On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
> > On 03/02/24 07:54:22, Shawn Guo wrote:
> > > On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
> > > >
> > > > Add myself as co-maintainer for Poplar board, as I'm currently
> > > > working on it (re-testing releases, addressing issues etc).
> > > >
> > > > CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> > > > CC: Shawn Guo <shawn.guo@linaro.org>
> > > > Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
> > >
> > > Acked-by: Shawn Guo <shawn.guo@linaro.org>
> > >
> > > I'm not actively working on poplar any more, so maybe remove me in the meantime.
> >
> >
> > hi Igor,
> >
> > Yes please go ahead and thanks for offering.
> >
> > I'll sync with you later next week (I found my Poplar in storage, so maybe we cam improve things a little)
> > Also it would be good if we knew there are still users.
> >
> >
> > Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> >
> Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is
> very similar to the Hi3798CV200 SoC and many peripherals and drivers can be
> reused. I think you can try moving arch/arm/include/asm/arch-hi3798cv200 to
> arch/arm/mach-histb and let's maintain all HiSTB series SoCs/boards under it
> altogether? The same thing also applies to TF-A. Currently upstream code
> refers to poplar everywhere but actually the port is portable enough to
> handle a lot of other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x
> etc..

Sure, if this is indeed a family we should do that (documentation was
scarce back them when I did the initial port).

maybe you'd like to take a stab Igor?


> > >
> > > Shawn
>

Re: [PATCH] poplar: add myself as co-maintainer

[Yang Xiwen]

On 2/3/2024 6:19 PM, Jorge Ramirez-Ortiz, Gmail wrote:
> On 03/02/24 17:45:42, Yang Xiwen wrote:
>> On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
>>> On 03/02/24 07:54:22, Shawn Guo wrote:
>>>> On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
>>>>>
>>>>> Add myself as co-maintainer for Poplar board, as I'm currently
>>>>> working on it (re-testing releases, addressing issues etc).
>>>>>
>>>>> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
>>>>> CC: Shawn Guo <shawn.guo@linaro.org>
>>>>> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
>>>>
>>>> Acked-by: Shawn Guo <shawn.guo@linaro.org>
>>>>
>>>> I'm not actively working on poplar any more, so maybe remove me in the meantime.
>>>
>>>
>>> hi Igor,
>>>
>>> Yes please go ahead and thanks for offering.
>>>
>>> I'll sync with you later next week (I found my Poplar in storage, so maybe we cam improve things a little)
>>> Also it would be good if we knew there are still users.
>>>
>>>
>>> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
>>>
>> Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is
>> very similar to the Hi3798CV200 SoC and many peripherals and drivers can be
>> reused. I think you can try moving arch/arm/include/asm/arch-hi3798cv200 to
>> arch/arm/mach-histb and let's maintain all HiSTB series SoCs/boards under it
>> altogether? The same thing also applies to TF-A. Currently upstream code
>> refers to poplar everywhere but actually the port is portable enough to
>> handle a lot of other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x
>> etc..
> 
> Sure, if this is indeed a family we should do that (documentation was
> scarce back them when I did the initial port).
About docs, I've got some. But still, some critical datasheets are 
missing. Most peripherals are the common ones, like DWC3(USB), 
PL061(GPIO), DWMMC(eMMC/SD), PL011(serial), SP905(watchdog). But there 
are some cores that are difficult to find docs. e.g. USB2 INNO PHY, USB3 
nano PHY, PMU, TZPC/TZASC, HDMI etc..

Please ping me if you find some documents about them. Especially PMU and 
USB PHYs, it's quite hard to write a mainline driver for them without 
datasheets.
> 
> maybe you'd like to take a stab Igor?
> 
> 
>>>>
>>>> Shawn
>>

Re: [PATCH] poplar: add myself as co-maintainer

[Igor Opaniuk]

Hi Yang,

On Sat, Feb 3, 2024 at 10:59 AM Yang Xiwen <forbidden405@foxmail.com> wrote:
>
> On 2/3/2024 5:45 PM, Yang Xiwen wrote:
> > On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
> >> On 03/02/24 07:54:22, Shawn Guo wrote:
> >>> On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk
> >>> <igor.opaniuk@foundries.io> wrote:
> >>>>
> >>>> Add myself as co-maintainer for Poplar board, as I'm currently
> >>>> working on it (re-testing releases, addressing issues etc).
> >>>>
> >>>> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> >>>> CC: Shawn Guo <shawn.guo@linaro.org>
> >>>> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
> >>>
> >>> Acked-by: Shawn Guo <shawn.guo@linaro.org>
> >>>
> >>> I'm not actively working on poplar any more, so maybe remove me in
> >>> the meantime.
> >>
> >>
> >> hi Igor,
> >>
> >> Yes please go ahead and thanks for offering.
> >>
> >> I'll sync with you later next week (I found my Poplar in storage, so
> >> maybe we cam improve things a little)
> >> Also it would be good if we knew there are still users.
> >>
> >>
> >> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> >>
> > Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is
> > very similar to the Hi3798CV200 SoC and many peripherals and drivers can
> > be reused. I think you can try moving
> > arch/arm/include/asm/arch-hi3798cv200 to arch/arm/mach-histb and let's
> > maintain all HiSTB series SoCs/boards under it altogether? The same
> > thing also applies to TF-A. Currently upstream code refers to poplar
> > everywhere but actually the port is portable enough to handle a lot of
> > other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x etc..
> There are some patches i sent pending for review. They are mostly
> originally sent just for Hi3798MV200, but the framework(such as
> drivers/clk/hisilicon) can be also used for poplar too. I hope you guys
> can take a look at them[1] and give your opinions about them(RBs and
> Acks are welcomed).
Sure, I'll take a look during this week .

>
> [1] HiSi clk framework:
> https://lore.kernel.org/u-boot/20240119-b4-hisi-clk-v1-0-279e38c95ca2@outlook.com/
> >>>
> >>> Shawn
> >
>


-- 
Best regards - Freundliche Grüsse - Meilleures salutations

Igor Opaniuk
Senior Software Engineer, Embedded & Security
E: igor.opaniuk@foundries.io
W: www.foundries.io

Re: [PATCH] poplar: add myself as co-maintainer

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

On Fri, Feb 02, 2024 at 10:44:29PM +0100, Igor Opaniuk wrote:

> Add myself as co-maintainer for Poplar board, as I'm currently
> working on it (re-testing releases, addressing issues etc).
> 
> CC: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
> CC: Shawn Guo <shawn.guo@linaro.org>
> Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
> Acked-by: Shawn Guo <shawn.guo@linaro.org>
> Acked-by: Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]