Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2945583ybc; Thu, 21 Nov 2019 00:32:38 -0800 (PST) X-Google-Smtp-Source: APXvYqzm1i0q8JQ5oObMigIk3+fEpwyudIF5meN/tuih3Kf6CPDdhTxz9mdwy9eanztd1nYLnxFs X-Received: by 2002:a17:906:f756:: with SMTP id jp22mr11795878ejb.234.1574325158481; Thu, 21 Nov 2019 00:32:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574325158; cv=none; d=google.com; s=arc-20160816; b=Svh+wOmU2ml3YuYbYo8XhOrzkNXkWz00KcPqfYSSbJ2PWtTgJ0MGrlGY+qZIR5aFNL umm0GJnwGBFUgFSXIScykm36aFimPIw7xQ8J7Dl198c1N72z20x0NXykAhUsKz/b85Nr q1RyandCf3ji3qV/EW/6AEU7yTsQ8GCbsihBcLW9N6ErqOxobkUPjF6F/+IfoZ117SUQ DBpL4HcHKeT+8UMz0EFYNXFWs9f+p8tVy9ajpcUvCjRjCOW4JtYYApooAAGrLAXXMQbS 3fbv5nWjBc+V3rcq6inmtj5tmFsa6wDoj3udhb7ppHaOdvT7GYNlRnhwXORN9rnnzlzT 84Dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=5+g9mn+AxAnxlklqw4XxoiWzE23UWdDQPBVvzz3xiQM=; b=J7NDZgCDXh4KyICpk+d5NDVKL7LrPjq1Na+9hNuCMnivlQhcotgwU3AkFoTw39I+1r O5gySnK0CepstajmH4f5Q9cT0tb89lUwG1IIhQcRZABhlLwUON4rXFUzHrSl2kwILqGf weIMB4Agb4l+ztCrHfTCUP7n1yX9s37XDXqlO8uxfAnTj/kgMH4/zdZ5r1P1uOa4z3Nr uycCuUzX1U4QG7nkP8+iRI2Gij27m1FgfJAiWWajCfBP6xC8b63hxHUedEiWi3q0mDHo ADEf/gzQOF8aw6cwzjol24OjEmIfRCoyu2HnDjAAGiONtzw5kB3c0K7lRU59Duj2bwVi M0Jg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x26si1524834eda.404.2019.11.21.00.32.12; Thu, 21 Nov 2019 00:32:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726701AbfKUIar (ORCPT + 99 others); Thu, 21 Nov 2019 03:30:47 -0500 Received: from mail-oi1-f196.google.com ([209.85.167.196]:40954 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726132AbfKUIaq (ORCPT ); Thu, 21 Nov 2019 03:30:46 -0500 Received: by mail-oi1-f196.google.com with SMTP id d22so2440684oic.7; Thu, 21 Nov 2019 00:30:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5+g9mn+AxAnxlklqw4XxoiWzE23UWdDQPBVvzz3xiQM=; b=TGhylNBCc9abQIyDXjCjh2uu+Q5IWIXMpA9HFLxBbd0GATUqEnEunZNOePubC/dLFn gRl00cHzNMphnflP/pNE+n3zHoICAuI4pR2WcEybXslon3bmWUD+9o+CN+FT3gp9XwPx gQAAh37M2EIKT2ywqXkdWwW5G5lAlbXCEnCENV1fqfMF6qzZbNt5OVed3D2T8j8k1dHT NhOdekI0Wh9/N5upsgz3yCOSuCNVtFV2XFKqGaayGdH7oldfQ2TCdSVWCkUZ0zRhGdRl 0W9qE4vf0zxPiwSOKsKfvjNdUPBrG2WcbkROzQ97dqGPRmcXmsOdMGj4BtyhYCymYA67 R1mQ== X-Gm-Message-State: APjAAAWxD3UNS0JCZ7+vDyrsNr4gX7NKx/qHX+eXMOdsev2sntuZzQLk Sv9SIW82VkUkzVjuglf80kV5TsH8G0R05ZRTN+HujrbS X-Received: by 2002:aca:3a86:: with SMTP id h128mr6308515oia.131.1574325045753; Thu, 21 Nov 2019 00:30:45 -0800 (PST) MIME-Version: 1.0 References: <20191121080954.14915-1-peter.ujfalusi@ti.com> In-Reply-To: <20191121080954.14915-1-peter.ujfalusi@ti.com> From: Geert Uytterhoeven Date: Thu, 21 Nov 2019 09:30:34 +0100 Message-ID: Subject: Re: [PATCH] spi: pic32: Retire dma_request_slave_channel_compat() To: Peter Ujfalusi Cc: Mark Brown , Vinod , linux-spi , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter, On Thu, Nov 21, 2019 at 9:11 AM Peter Ujfalusi wrote: > There is no reason to use the dma_request_slave_channel_compat() as no > filter function and parameter is provided. > > Switch the driver to use dma_request_chan() instead. > > Signed-off-by: Peter Ujfalusi > --- a/drivers/spi/spi-pic32.c > +++ b/drivers/spi/spi-pic32.c > @@ -609,22 +609,18 @@ static void pic32_spi_cleanup(struct spi_device *spi) > static void pic32_spi_dma_prep(struct pic32_spi *pic32s, struct device *dev) > { > struct spi_master *master = pic32s->master; > - dma_cap_mask_t mask; > > - dma_cap_zero(mask); > - dma_cap_set(DMA_SLAVE, mask); > - > - master->dma_rx = dma_request_slave_channel_compat(mask, NULL, NULL, > - dev, "spi-rx"); > - if (!master->dma_rx) { > + master->dma_rx = dma_request_chan(dev, "spi-rx"); Why not dma_request_slave_channel()? That way you... > + if (IS_ERR(master->dma_rx)) { ... don't have to change the NULL check here, and... > dev_warn(dev, "RX channel not found.\n"); > + master->dma_rx = NULL; ... don't have to override by NULL here. (same for TX below). Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds