Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162271AbbKTN4i (ORCPT ); Fri, 20 Nov 2015 08:56:38 -0500 Received: from mail-wm0-f52.google.com ([74.125.82.52]:33661 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161540AbbKTN4g (ORCPT ); Fri, 20 Nov 2015 08:56:36 -0500 MIME-Version: 1.0 In-Reply-To: References: <1447948422-4915-1-git-send-email-mweseloh42@gmail.com> <1447948422-4915-2-git-send-email-mweseloh42@gmail.com> Date: Fri, 20 Nov 2015 14:56:34 +0100 Message-ID: Subject: Re: [linux-sunxi] [PATCH] spi: dts: sun4i: Add support for inter-word wait cycles using the SPI Wait Clock Register From: Marcus Weseloh To: Julian Calaby Cc: linux-sunxi , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Maxime Ripard , Mark Brown , devicetree , "Mailing List, Arm" , "linux-kernel@vger.kernel.org" , linux-spi@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1034 Lines: 29 Hi Julien, 2015-11-20 11:12 GMT+01:00 Julian Calaby : > Having magic numbers is kind-of a drivers' job. Yes, of course. What I meant was that I didn't feel comfortable to include this magic number in driver code because I'm not 100% sure if it is correct across all SPI configurations and SoCs that this driver supports (A10 / A20). > (and the wdelay should > arguably be a core-spi thing, not a sunxi thing, but that's a separate > discussion) I've been thinking about that, but it seemed to big a change to attempt with my limited kernel hacking experience. Mark, do you think we should rather talk about adding support for options like this delay to spi-core? Or would it be OK to add it to the sun4i driver and possibly refactor later? Cheers, Marcus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/