All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <samuel@sholland.org>, <wens@csie.org>, <jernej.skrabec@gmail.com>
Cc: <arnd@arndb.de>, <hdegoede@redhat.com>, <icenowy@aosc.io>,
	<krzysztof.kozlowski+dt@linaro.org>, <mripard@kernel.org>,
	<robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-sunxi@lists.linux.dev>
Subject: Re: [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 support
Date: Mon, 15 Aug 2022 06:59:47 +0000	[thread overview]
Message-ID: <de99e42e-e721-834a-e532-ace515f70ba7@microchip.com> (raw)
In-Reply-To: <095cb5ca-3e63-50b0-f604-4c8c226f67e0@microchip.com>

On 15/08/2022 07:57, Conor Dooley wrote:
> Hey Samuel,
> On 15/08/2022 05:12, Samuel Holland wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> This series cleans up a few issues in the system controller driver, and
>> then expands the exported regmap to support one of the pairs of LDOs
>> built in to the D1 SoC.
>>
>> Eventually, we will need to update the SRAM region claiming API so
>> ownership can be swapped back and forth by consumer drivers. This will
>> be necessary for uploading firmware to the R329/D1 DSPs, but it is not
>> needed for initial bringup.
> 
> I tried this series on top of both 6.0-rc1 & next, but I saw a shed
> load of errors from dtbs_check. I'll take a look at the rest of the
> series later on, but just FYI. I know I have seen patches going into
> different subsystems so I assume you're working on it. However, it
> would be nice to let us what all the dependencies for this series are
> dt-binding wise in the cover letter.
> I have been trying to get riscv down to 0 warnings and would not be
> in favour of accepting patches that go in the other direction.
> (This patchset currently produces about 75 warnings)
> 

Ignore this, I read the wrong cover letter. Sorry.

WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <samuel@sholland.org>, <wens@csie.org>, <jernej.skrabec@gmail.com>
Cc: <arnd@arndb.de>, <hdegoede@redhat.com>, <icenowy@aosc.io>,
	<krzysztof.kozlowski+dt@linaro.org>, <mripard@kernel.org>,
	<robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-sunxi@lists.linux.dev>
Subject: Re: [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 support
Date: Mon, 15 Aug 2022 06:59:47 +0000	[thread overview]
Message-ID: <de99e42e-e721-834a-e532-ace515f70ba7@microchip.com> (raw)
In-Reply-To: <095cb5ca-3e63-50b0-f604-4c8c226f67e0@microchip.com>

On 15/08/2022 07:57, Conor Dooley wrote:
> Hey Samuel,
> On 15/08/2022 05:12, Samuel Holland wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> This series cleans up a few issues in the system controller driver, and
>> then expands the exported regmap to support one of the pairs of LDOs
>> built in to the D1 SoC.
>>
>> Eventually, we will need to update the SRAM region claiming API so
>> ownership can be swapped back and forth by consumer drivers. This will
>> be necessary for uploading firmware to the R329/D1 DSPs, but it is not
>> needed for initial bringup.
> 
> I tried this series on top of both 6.0-rc1 & next, but I saw a shed
> load of errors from dtbs_check. I'll take a look at the rest of the
> series later on, but just FYI. I know I have seen patches going into
> different subsystems so I assume you're working on it. However, it
> would be nice to let us what all the dependencies for this series are
> dt-binding wise in the cover letter.
> I have been trying to get riscv down to 0 warnings and would not be
> in favour of accepting patches that go in the other direction.
> (This patchset currently produces about 75 warnings)
> 

Ignore this, I read the wrong cover letter. Sorry.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-15  6:59 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  4:12 [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 support Samuel Holland
2022-08-15  4:12 ` Samuel Holland
2022-08-15  4:12 ` [PATCH v2 01/10] dt-bindings: sram: sunxi-sram: Clean up the compatible lists Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 12:15   ` Andre Przywara
2022-08-15 12:15     ` Andre Przywara
2022-08-15 13:54   ` Heiko Stübner
2022-08-15 13:54     ` Heiko Stübner
2022-08-16  5:55   ` Krzysztof Kozlowski
2022-08-16  5:55     ` Krzysztof Kozlowski
2022-08-15  4:12 ` [PATCH v2 02/10] dt-bindings: sram: sunxi-sram: Add D1 compatible string Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 13:55   ` Heiko Stübner
2022-08-15 13:55     ` Heiko Stübner
2022-08-16  7:46   ` Krzysztof Kozlowski
2022-08-16  7:46     ` Krzysztof Kozlowski
2022-08-15  4:12 ` [PATCH v2 03/10] soc: sunxi: sram: Actually claim SRAM regions Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 13:56   ` Heiko Stübner
2022-08-15 13:56     ` Heiko Stübner
2022-08-15  4:12 ` [PATCH v2 04/10] soc: sunxi: sram: Prevent the driver from being unbound Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:00   ` Heiko Stübner
2022-08-15 14:00     ` Heiko Stübner
2022-08-15  4:12 ` [PATCH v2 05/10] soc: sunxi: sram: Fix probe function ordering issues Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:06   ` Heiko Stübner
2022-08-15 14:06     ` Heiko Stübner
2022-08-16  0:05     ` Samuel Holland
2022-08-16  0:05       ` Samuel Holland
2022-08-15  4:12 ` [PATCH v2 06/10] soc: sunxi: sram: Fix debugfs info for A64 SRAM C Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15  4:12 ` [PATCH v2 07/10] soc: sunxi: sram: Return void from the release function Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:09   ` Heiko Stübner
2022-08-15 14:09     ` Heiko Stübner
2022-08-15  4:12 ` [PATCH v2 08/10] soc: sunxi: sram: Save a pointer to the OF match data Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:10   ` Heiko Stübner
2022-08-15 14:10     ` Heiko Stübner
2022-08-15  4:12 ` [PATCH v2 09/10] soc: sunxi: sram: Export the LDO control register Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:13   ` Heiko Stübner
2022-08-15 14:13     ` Heiko Stübner
2022-08-15  4:12 ` [PATCH v2 10/10] soc: sunxi: sram: Add support for the D1 system control Samuel Holland
2022-08-15  4:12   ` Samuel Holland
2022-08-15 14:14   ` Heiko Stübner
2022-08-15 14:14     ` Heiko Stübner
2022-08-15  6:58 ` [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 support Conor.Dooley
2022-08-15  6:58   ` Conor.Dooley
2022-08-15  6:59   ` Conor.Dooley [this message]
2022-08-15  6:59     ` Conor.Dooley
2022-09-18 21:49 ` Jernej Škrabec
2022-09-18 21:49   ` Jernej Škrabec

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=de99e42e-e721-834a-e532-ace515f70ba7@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=icenowy@aosc.io \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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.