From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752088AbeAZVol (ORCPT <rfc822;w@1wt.eu>);
        Fri, 26 Jan 2018 16:44:41 -0500
Received: from mail-qt0-f178.google.com ([209.85.216.178]:44679 "EHLO
        mail-qt0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751748AbeAZVoi (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 26 Jan 2018 16:44:38 -0500
X-Google-Smtp-Source: AH8x225n1CJpVhFQStsxuWKu6ANT4QpGRAjZIE+keewd4USg7M2SxFMXoWmVlRYcWjysWr1xjZBBsw==
Message-ID: <1517003075.32074.29.camel@ndufresne.ca>
Subject: Re: [RFC PATCH 6/8] v4l2: document the request API interface
From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Randy Dunlap <rdunlap@infradead.org>,
        Alexandre Courbot <acourbot@chromium.org>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        Hans Verkuil <hverkuil@xs4all.nl>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        Pawel Osciak <posciak@chromium.org>,
        Marek Szyprowski <m.szyprowski@samsung.com>,
        Tomasz Figa <tfiga@chromium.org>,
        Sakari Ailus <sakari.ailus@linux.intel.com>,
        Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Date: Fri, 26 Jan 2018 16:44:35 -0500
In-Reply-To: <98ccb2f3-156e-2f4e-4630-9d16d157d65b@infradead.org>
References: <20180126060216.147918-1-acourbot@chromium.org>
         <20180126060216.147918-7-acourbot@chromium.org>
         <98ccb2f3-156e-2f4e-4630-9d16d157d65b@infradead.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 (3.26.4-1.fc27) 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Le vendredi 26 janvier 2018 à 12:40 -0800, Randy Dunlap a écrit :
> > +Request API
> > +===========
> > +
> > +The Request API has been designed to allow V4L2 to deal with
> > requirements of
> > +modern IPs (stateless codecs, MIPI cameras, ...) and APIs (Android
> > Codec v2).
> 
> Hi,
> Just a quick question:  What are IPs?
> 
> Not Internet Protocols. Hopefully not Intellectual Properties.
> Maybe Intelligent Processors?

Stands for "Intellectual Property". Used like this, I believe it's a
bit of a slang. It's also slightly pejorative as we often assume that
self contained "IP Cores" are proprietary black box. But considering
all the security issues that was found in these black boxes firmwares,
it's kind of fair criticism.

Nicolas

p.s. I'd propose to rephrase this in later version