From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25A26C43215 for ; Mon, 25 Nov 2019 09:27:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F0CC720836 for ; Mon, 25 Nov 2019 09:27:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="OOA0opZB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727237AbfKYJ1I (ORCPT ); Mon, 25 Nov 2019 04:27:08 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:52195 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726498AbfKYJ1I (ORCPT ); Mon, 25 Nov 2019 04:27:08 -0500 Received: by mail-wm1-f68.google.com with SMTP id g206so14329535wme.1 for ; Mon, 25 Nov 2019 01:27:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GPEnZNQEI8QKSUnH82DWjy/DOlQPOIbDIUbMCpH13uc=; b=OOA0opZBwLH1JTUMyzqDx7FpKLojjoTy9X8fiOzRNOUWulU66lRwhIvTVGOuHvcxBl i/K1roaWlbflWdjCp7QQe6ijp6djt7dCmenW/J0ANIQKISO97fqvVaNTvCwg0lhWJ6dw rsMNCoR0PoOqpI8TWhuGSd5fiwceT33EZlFXNVJ4hGOCwK7rZNWheXzjcX69rWSqnJzj pYty3+YuzE/DHBIIypzKck8vwiwffrmFxLjHGH0FGMbSukhgjzqeXKpj8c+yAaQ/aa9o YJA70p3Q5Gq4FexTAP0jF3HKgrzvuV8v5qaM7oVAinr7H04qfxHUuPq4/Wxs6NfnA7IR aU9g== 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=GPEnZNQEI8QKSUnH82DWjy/DOlQPOIbDIUbMCpH13uc=; b=kyAXcndRn6XpBvNKBbaP23M7L679ZkJU88MDcaCg88bapMRHTZH9KjsDlmqIyP8m4W 8sBXr3d4H5oaCPM/ueao2MzcS/JZVdMhN+mMehWNRBibi5WE1Sc9EVrdliTBlwitgyhS HZLky9j9INkKZ/T5M6RmgRWWJ7UvSBakaL99cTjcXc+J/UH6xnJmUqEwBy4CPVbADEGx 8VLPHtMmd3ESb60LCl8seQgo9g60ryFwicaT72UgEBzoWmFM2g1MFjCNtP7+7Lx7RU2m o/XsbEO8qq16WRSUKeSFAMsCVDF/lFoTwzFl2vAqs9BuWHJLrZWOToTeV/pJU12vGOQj KPCg== X-Gm-Message-State: APjAAAV7EHMzsXPp6dPuzOwjcmP1i7rN2pXsD0tvh4u5+R4RUR8LLtqZ JAWShMUm8Jd/D9oFSUmHJy3CfI7m8iXU+VfJTg0= X-Google-Smtp-Source: APXvYqxzdo3Q5FMwIo3FbQht8mabp2Hsamcv3s8jm+BuubQR5plKLDThjkZYoeVig7g/1dob+nT2rjG4fWtkPMX7IRI= X-Received: by 2002:a05:600c:228c:: with SMTP id 12mr20671074wmf.154.1574674026240; Mon, 25 Nov 2019 01:27:06 -0800 (PST) MIME-Version: 1.0 References: <20191122205153.30723-1-adham.abozaeid@microchip.com> In-Reply-To: <20191122205153.30723-1-adham.abozaeid@microchip.com> From: Julian Calaby Date: Mon, 25 Nov 2019 20:26:55 +1100 Message-ID: Subject: Re: [PATCH 1/4] staging: wilc1000: use runtime configuration for sdio oob interrupt To: Adham Abozaeid Cc: linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, Greg KH , Johannes Berg , Ajay Singh Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi Adham, On Sat, Nov 23, 2019 at 7:55 AM wrote: > > From: Ajay Singh > > Set SDIO Out-of-band interrupt configuration at run time by passing > parameter during module load. The OOB interrupt is a GPIO and this is an SDIO card, so why not just set the relevant pin in the devicetree and detect it based on that? I'm pretty sure that the Broadcom fmac driver does something like this. Thanks, -- Julian Calaby Email: julian.calaby@gmail.com Profile: http://www.google.com/profiles/julian.calaby/