linux-kernel - Re: [PATCH v2 47/67] media: platform: rename sunxi/ to allwinner/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220316141357.2a460bf3@coco.lan>
Date:   Wed, 16 Mar 2022 14:13:57 +0100
From:   Mauro Carvalho Chehab <mchehab@...nel.org>
To:     Jernej Škrabec <jernej.skrabec@...il.com>
Cc:     Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Niklas Söderlund 
        <niklas.soderlund+renesas@...natech.se>,
        Cai Huoqing <caihuoqing@...du.com>,
        Chen-Yu Tsai <wens@...e.org>,
        Dinghao Liu <dinghao.liu@....edu.cn>,
        Dmitry Osipenko <digetx@...il.com>,
        Eugen Hristev <eugen.hristev@...rochip.com>,
        Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
        Hans Verkuil <hverkuil-cisco@...all.nl>,
        Jacopo Mondi <jacopo@...ndi.org>,
        Jia-Ju Bai <baijiaju1990@...il.com>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Maxime Ripard <mripard@...nel.org>,
        Mikhail Rudenko <mike.rudenko@...il.com>,
        Ming Qian <ming.qian@....com>,
        Ondrej Jirman <megous@...ous.com>,
        Robert Foss <robert.foss@...aro.org>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
        Yong Deng <yong.deng@...ewell.com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-media@...r.kernel.org, linux-sunxi@...ts.linux.dev
Subject: Re: [PATCH v2 47/67] media: platform: rename sunxi/ to allwinner/

Em Tue, 15 Mar 2022 19:04:05 +0100
Jernej Škrabec <jernej.skrabec@...il.com> escreveu:

> > > By organizing entries per vendor, while we may need to do puntual
> > > per-vendor adjustments when they rename and change IP with other
> > > vendors, the global platform Kconfig/Make will contain a single entry
> > > per vendor. I can't foresee any need to change this in the future,
> > > if we take care of keeping the entries there properly sorted.
> > > 
> > > With regards to naming the per-vendor directory, while I do prefer to have
> > > the  directories named after the vendor, and not after a vendor's nick 
> > > name, It should also be ok to use a vendor's nick name, provided that 
> > > such name is meant to be used by all their current and future IP.
> > > 
> > > Not sure if "sunxi" is actually a vendor's nick name. It sounds
> > > much likely that it is, instead, a brand name that covers their 
> > > current media-related SoC. 
> > > 
> > > Can someone from the vendor shed a light on it?  
> 
> Allwinner (as a company) isn't directly involved in maintaining upstream Linux 
> support. Drivers are provided by linux-sunxi community, sometimes by cleaning 
> up vendor drivers or more often by writing them from scratch.
> 
> That being said, "sunxi" is extensively used in vendor kernel, most often it's 
> directory name containing vendor specific driver. It's derived from SoC family 
> name, like sun4i, sun5i, sun5i, sun50i, etc. where number is replaced with X.
> 
> sunxi is synonym for Allwinner basically from the start. Community build 
> around these SoCs is called linux-sunxi and even entry in MAINTAINERS contains 
> both names: "ARM/Allwinner sunXi SoC support". Note that sunxi is not limited 
> to ARM SoCs. RISC-V family is called sun20i.
> 
> Hope this helps.

Ok, so let's then keep it named as "sunxi", and place all drivers from 
Allwinner there.

Thanks,
Mauro