On Tue, Mar 21, 2017 at 2:48 PM, Vinod Koul <vinod.koul@xxxxxxxxx> wrote: > On Tue, Mar 21, 2017 at 02:17:21PM +0530, Anup Patel wrote: >> On Tue, Mar 21, 2017 at 2:00 PM, Vinod Koul <vinod.koul@xxxxxxxxx> wrote: >> > On Mon, Mar 06, 2017 at 03:13:24PM +0530, Anup Patel wrote: >> >> The Broadcom SBA RAID is a stream-based device which provides >> >> RAID5/6 offload. >> >> >> >> It requires a SoC specific ring manager (such as Broadcom FlexRM >> >> ring manager) to provide ring-based programming interface. Due to >> >> this, the Broadcom SBA RAID driver (mailbox client) implements >> >> DMA device having one DMA channel using a set of mailbox channels >> >> provided by Broadcom SoC specific ring manager driver (mailbox >> >> controller). >> >> >> >> The Broadcom SBA RAID hardware requires PQ disk position instead >> >> of PQ disk coefficient. To address this, we have added raid_gflog >> >> table which will help driver to convert PQ disk coefficient to PQ >> >> disk position. >> >> >> >> This patchset is based on Linux-4.11-rc1 and depends on patchset >> >> "[PATCH v5 0/2] Broadcom FlexRM ring manager support" >> > >> > Okay I applied and was about to push when I noticed this :( >> > >> > So what is the status of this..? >> >> PATCH2 is Acked but PATCH1 is under-review. Currently, its >> v6 of that patchset. >> >> The only dependency on that patchset is the changes in >> brcm-message.h which are required by this BCM-SBA-RAID >> driver. >> >> @Jassi, >> Can you please have a look at PATCH v6? > > And I would need an immutable branch/tag once merged. I am going to keep > this series pending till then. The Broadcom FlexRM patchset is pickedup by Jassi and can be found in mailbox-for-next branch of git://git.linaro.org/landing-teams/working/fujitsu/integration Both patchset (Broadcom FlexRM patchset and this one) are also available in sba-raid-v7 branch of https://github.com/Broadcom/arm64-linux.git Regards, Anup -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
