changing GFP_DMA32 to GFP_DMA

Using GFP_DMA for DMA allocations in a kernel code that runs on a 32-bit system should not inherently cause an error just because of the flag's usage. The GFP_DMA flag is used to indicate that the allocated memory is DMA-able, and it's generally used for devices that require direct access to physical memory without going through the CPU's caching mechanisms. This flag is not specifically tied to 32-bit or 64-bit addressing; it's more about the requirements of the device and the DMA (Direct Memory Access) system.

common/driver/axis_gen2.c

@@ -440,8 +440,8 @@ void AxisG2_Init(struct DmaDevice *dev) {
       hwData->writeHandle = virt_to_phys(hwData->writeAddr);
    } else {
       // Allocate coherent DMA buffers for read and write operations
-      hwData->readAddr = dma_alloc_coherent(dev->device, size, &(hwData->readHandle), GFP_DMA32 | GFP_KERNEL);
-      hwData->writeAddr = dma_alloc_coherent(dev->device, size, &(hwData->writeHandle), GFP_DMA32 | GFP_KERNEL);
+      hwData->readAddr = dma_alloc_coherent(dev->device, size, &(hwData->readHandle), GFP_DMA | GFP_KERNEL);
+      hwData->writeAddr = dma_alloc_coherent(dev->device, size, &(hwData->writeHandle), GFP_DMA | GFP_KERNEL);
    }
 
    // Log buffer addresses

common/driver/dma_buffer.c

@@ -101,7 +101,7 @@ size_t dmaAllocBuffers ( struct DmaDevice *dev, struct DmaBufferList *list,
       // Coherent buffer, map dma coherent buffers
       if ( list->dev->cfgMode & BUFF_COHERENT ) {
          buff->buffAddr =
-            dma_alloc_coherent(list->dev->device, list->dev->cfgSize, &(buff->buffHandle), GFP_DMA32 | GFP_KERNEL);
+            dma_alloc_coherent(list->dev->device, list->dev->cfgSize, &(buff->buffHandle), GFP_DMA | GFP_KERNEL);
       }
 
       // Streaming buffer type, standard kernel memory