Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp1392935pxy; Thu, 6 May 2021 07:10:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzB5x0yt47LAWOoreXi3uZBko8W+vfiS7WmlNVFQikKhKsUww2iqECT3l9jH2+pLQBY0EBj X-Received: by 2002:aa7:dc4e:: with SMTP id g14mr5525563edu.11.1620310219241; Thu, 06 May 2021 07:10:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620310219; cv=none; d=google.com; s=arc-20160816; b=gX7iGwsjm6ZJpF2Gbs3NTGYOgXirv0UbwxRXmUStXrA8YdgY/ZcQpljAfnY1Yiozko E/I4VeTSro+XO29kemckdaobmIzuJtQF7LAfQb088ff9fBx/pRI75/81uZgovotI78wI 4FVehW0dy5XyUCU9TraurH7/zDNxrBIvi7SizhqPxud0S1Yq3OKVGExTKc1pjQAIJn9t fKUU1xhiRpr/K55Gspd38Rn5fw6T2thSUURvl/VWzA2PtCEQYMULmFlNw28gHhFO4VGV SupkcCVvkW+o7XjClgTTOpbx2La92hKCZCcuS3eRpWaJqmzu0SGWHVKnI3rM5E2Dnlms vs4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=Q9h6o9ctEHc8iY8TpOG1bBkRBecU/A/rUbR2Rl7sVlc=; b=KY9oDMGnqS+/D0yvkL34devQHw/YjMtsGtXIK8YJHtRmyoJAn2HTU65aG1G9H09f8x HDxDsqlURjWCTkau5sukp9FCu12miJwSuyrCaLU4PPbWARFUnkny4PJ5tr5DGyMv51+f 2pHB+I9MjFpqTeOQfXm7482sGIZ0G2PWBxhOGc95jh2ZCaeVh5W6/5TDnCF3+2/yM5n4 J/XbWl+RKxJ08Eboc+7s5gQli3VHYMmEdRI/8ozwBB/iqrk1jrcV0gd4cA50Vkon50Na bPxTuGomVQT1q9cAStEeFkjDy+7dUJqCqrMBWn2Vc85kA2A3423b4KhDbXyraREUYPcp rSaA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hJ5w5FJo; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gapps.redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id fx23si2333687ejb.550.2021.05.06.07.09.53; Thu, 06 May 2021 07:10:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hJ5w5FJo; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gapps.redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234539AbhEFOK0 (ORCPT + 99 others); Thu, 6 May 2021 10:10:26 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:23161 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234490AbhEFOKY (ORCPT ); Thu, 6 May 2021 10:10:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620310166; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Q9h6o9ctEHc8iY8TpOG1bBkRBecU/A/rUbR2Rl7sVlc=; b=hJ5w5FJoRpa8otNMNgA5Lw4lue63jvCrA7Y9ha8vucYh/9G0rbMYq9QstjUfCZXoJ1xHb+ HtPJhqkbwpI7Cr5oDZC+lZOlyrKf7TGD6EZb/7aCXI7c9JvcIZ0Y21EGHHPm1xneqerRJK wcqvBx8BPEbbvWFU0bNkU2GE7XDZwJ8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-150-lKQauTevPp6sFzeJ1LyBoA-1; Thu, 06 May 2021 10:09:21 -0400 X-MC-Unique: lKQauTevPp6sFzeJ1LyBoA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4B388C73A3; Thu, 6 May 2021 14:09:20 +0000 (UTC) Received: from [10.10.110.34] (unknown [10.10.110.34]) by smtp.corp.redhat.com (Postfix) with ESMTP id EC71610016FD; Thu, 6 May 2021 14:09:18 +0000 (UTC) Message-ID: <24356aa7737d5d0bbf9481bbba89b4248811ebce.camel@gapps.redhat.com> Subject: Re: [PATCH V2 07/16] net: iosm: mbim control device From: Dan Williams To: "Kumar, M Chetan" , Loic Poulain Cc: Network Development , "linux-wireless@vger.kernel.org" , "johannes@sipsolutions.net" , "Sudi, Krishna C" , linuxwwan Date: Thu, 06 May 2021 09:09:18 -0500 In-Reply-To: References: <20210420161310.16189-1-m.chetan.kumar@intel.com> <20210420161310.16189-8-m.chetan.kumar@intel.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, 2021-05-06 at 10:44 +0000, Kumar, M Chetan wrote: > Hi Loic, > > > > > > > Implements a char device for MBIM protocol communication & > > > provides a > > > simple IOCTL for max transfer buffer size configuration. > > > > > > Signed-off-by: M Chetan Kumar > > > > Now that the initial wwan framework support landed, could you > > migrate to it > > for creating the MBIM 'WWAN port' instead of creating yet another > > char > > driver? I see you introduced an IOCTL for packet size, I see no > > objection to > > add that in the wwan core. > > > > Sure, we have started the migration to MBIM 'WWAN port'. The next > version of patch > would contain these adaptations. > > If wwan core supports IOCTL for packet size, then we shall remove > that piece of > implementation in driver code. There has got to be a better way to do that than an ioctl. ioctls are not looked on favorably these days. Usually it's sysfs files or netlink config instead. Dan