All of lore.kernel.org
 help / color / mirror / Atom feed
From: Melissa Wen <mwen@igalia.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 10:05:56 -0100	[thread overview]
Message-ID: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com> (raw)
In-Reply-To: <40f27e32-720a-2f51-2164-5e152f53443a@redhat.com>

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

On 06/08, Javier Martinez Canillas wrote:
> Hello Melissa,
> 
> On 6/8/22 17:51, Melissa Wen wrote:
> 
> [snip]
> 
> >>>
> >>> I can take the last 3 patches through the Broadcom ARM SoC pull request, 
> >>> but the first three should probably go via the DRM tree unless you want 
> >>> me to merge them all?
> >>
> >> I can merge the first 3 patches through the drm-misc tree. Can I get
> >> an ack from you for those ?
> >>
> >> The changes are independent so there's no need for an immutable branch
> >> or any kind of cross tree coordination.
> > 
> > Hi Javier,
> > 
> > I'm not sure if you're suggesting here to apply the entire series as it
> > is now.
> >
> 
> No. I suggested that could just apply the first 3 patches that were related
> to DRM, not the last 3 three since Florian will pick those.
>  
> > I'm not able to have a functional kernel from arm defconfig, only for
> > arm64. I'd like to have this issue clarified before merge this serie. I
> > tried multi_v7_defconfig on raspbian 32-bits and got a kernel panic.
> > Things work better when using downstream bcm2711_defconfig.
> > 
> > If you have an idea of what is going on, please, let me know. I can try
> 
> Can you please share for info? For example your boot log when it panics,
> maybe that could shed some light on what's going on.
> 
> > again and I'll be okay on merging it. Otherwise, let's wait for more
> > inputs to have a better picture of the situation.
> >
> 
> Of course I don't plan to push patches that are known to cause issues.
> 
> I mentioned that could help merging the DRM changes if needed before
> you sent your bug report.

Hi Javier,

Thanks for waiting a little.

Stefan guided me to the missing part and I'm okay on this serie.

If there's any r-b missing for drm/v3d, you can add mine:
Reviewed-by: Melissa Wen <mwen@igalia.com>

But if you prefer that I applied them, just let me know.

Best Regards,

Melissa

> 
> -- 
> Best regards,
> 
> Javier Martinez Canillas
> Linux Engineering
> Red Hat
> 

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

WARNING: multiple messages have this Message-ID (diff)
From: Melissa Wen <mwen@igalia.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	devicetree@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Emma Anholt <emma@anholt.net>, Arnd Bergmann <arnd@arndb.de>,
	David Airlie <airlied@linux.ie>,
	Catalin Marinas <catalin.marinas@arm.com>,
	dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Peter Robinson <pbrobinson@gmail.com>,
	maxime@cerno.tech, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 10:05:56 -0100	[thread overview]
Message-ID: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com> (raw)
In-Reply-To: <40f27e32-720a-2f51-2164-5e152f53443a@redhat.com>

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

On 06/08, Javier Martinez Canillas wrote:
> Hello Melissa,
> 
> On 6/8/22 17:51, Melissa Wen wrote:
> 
> [snip]
> 
> >>>
> >>> I can take the last 3 patches through the Broadcom ARM SoC pull request, 
> >>> but the first three should probably go via the DRM tree unless you want 
> >>> me to merge them all?
> >>
> >> I can merge the first 3 patches through the drm-misc tree. Can I get
> >> an ack from you for those ?
> >>
> >> The changes are independent so there's no need for an immutable branch
> >> or any kind of cross tree coordination.
> > 
> > Hi Javier,
> > 
> > I'm not sure if you're suggesting here to apply the entire series as it
> > is now.
> >
> 
> No. I suggested that could just apply the first 3 patches that were related
> to DRM, not the last 3 three since Florian will pick those.
>  
> > I'm not able to have a functional kernel from arm defconfig, only for
> > arm64. I'd like to have this issue clarified before merge this serie. I
> > tried multi_v7_defconfig on raspbian 32-bits and got a kernel panic.
> > Things work better when using downstream bcm2711_defconfig.
> > 
> > If you have an idea of what is going on, please, let me know. I can try
> 
> Can you please share for info? For example your boot log when it panics,
> maybe that could shed some light on what's going on.
> 
> > again and I'll be okay on merging it. Otherwise, let's wait for more
> > inputs to have a better picture of the situation.
> >
> 
> Of course I don't plan to push patches that are known to cause issues.
> 
> I mentioned that could help merging the DRM changes if needed before
> you sent your bug report.

Hi Javier,

Thanks for waiting a little.

Stefan guided me to the missing part and I'm okay on this serie.

If there's any r-b missing for drm/v3d, you can add mine:
Reviewed-by: Melissa Wen <mwen@igalia.com>

But if you prefer that I applied them, just let me know.

Best Regards,

Melissa

> 
> -- 
> Best regards,
> 
> Javier Martinez Canillas
> Linux Engineering
> Red Hat
> 

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

WARNING: multiple messages have this Message-ID (diff)
From: Melissa Wen <mwen@igalia.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 10:05:56 -0100	[thread overview]
Message-ID: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com> (raw)
In-Reply-To: <40f27e32-720a-2f51-2164-5e152f53443a@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2073 bytes --]

On 06/08, Javier Martinez Canillas wrote:
> Hello Melissa,
> 
> On 6/8/22 17:51, Melissa Wen wrote:
> 
> [snip]
> 
> >>>
> >>> I can take the last 3 patches through the Broadcom ARM SoC pull request, 
> >>> but the first three should probably go via the DRM tree unless you want 
> >>> me to merge them all?
> >>
> >> I can merge the first 3 patches through the drm-misc tree. Can I get
> >> an ack from you for those ?
> >>
> >> The changes are independent so there's no need for an immutable branch
> >> or any kind of cross tree coordination.
> > 
> > Hi Javier,
> > 
> > I'm not sure if you're suggesting here to apply the entire series as it
> > is now.
> >
> 
> No. I suggested that could just apply the first 3 patches that were related
> to DRM, not the last 3 three since Florian will pick those.
>  
> > I'm not able to have a functional kernel from arm defconfig, only for
> > arm64. I'd like to have this issue clarified before merge this serie. I
> > tried multi_v7_defconfig on raspbian 32-bits and got a kernel panic.
> > Things work better when using downstream bcm2711_defconfig.
> > 
> > If you have an idea of what is going on, please, let me know. I can try
> 
> Can you please share for info? For example your boot log when it panics,
> maybe that could shed some light on what's going on.
> 
> > again and I'll be okay on merging it. Otherwise, let's wait for more
> > inputs to have a better picture of the situation.
> >
> 
> Of course I don't plan to push patches that are known to cause issues.
> 
> I mentioned that could help merging the DRM changes if needed before
> you sent your bug report.

Hi Javier,

Thanks for waiting a little.

Stefan guided me to the missing part and I'm okay on this serie.

If there's any r-b missing for drm/v3d, you can add mine:
Reviewed-by: Melissa Wen <mwen@igalia.com>

But if you prefer that I applied them, just let me know.

Best Regards,

Melissa

> 
> -- 
> Best regards,
> 
> Javier Martinez Canillas
> Linux Engineering
> Red Hat
> 

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-10 11:06 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  9:26 [PATCH v6 0/6] Raspberry PI 4 V3D enablement Peter Robinson
2022-06-03  9:26 ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 2/6] drm/v3d: Get rid of pm code Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03 11:29   ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03  9:26 ` [PATCH v6 3/6] drm/v3d: Add support for bcm2711 Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:07   ` Florian Fainelli
2022-06-13 17:07     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 5/6] ARM: configs: Enable DRM_V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 6/6] arm64: config: " Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-08  9:26 ` [PATCH v6 0/6] Raspberry PI 4 V3D enablement Florian Fainelli
2022-06-08  9:26   ` Florian Fainelli
2022-06-08 12:23   ` Javier Martinez Canillas
2022-06-08 12:23     ` Javier Martinez Canillas
2022-06-08 15:51     ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 16:48       ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-10 11:05         ` Melissa Wen [this message]
2022-06-10 11:05           ` Melissa Wen
2022-06-10 11:05           ` Melissa Wen
2022-06-10 12:13           ` Javier Martinez Canillas
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-13  9:30             ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-08 12:51 ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 22:35   ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-10 10:39     ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220610110556.63mddbye7vxq6mzb@mail.igalia.com \
    --to=mwen@igalia.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=maxime@cerno.tech \
    --cc=nsaenz@kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.