Em Tue, 15 Mar 2022 19:04:05 +0100
Jernej Škrabec <[email protected]> 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