[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86e1eb1f-7d12-7ffb-da5b-e6ab3ce85184@kernel.org>
Date: Wed, 27 Jul 2022 13:54:09 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jiho Chu <jiho.chu@...sung.com>, gregkh@...uxfoundation.org,
arnd@...db.de, linux-kernel@...r.kernel.org
Cc: yelini.jeong@...sung.com, myungjoo.ham@...sung.com
Subject: Re: [PATCH 1/9] trinity: Add base driver
On 25/07/2022 08:53, Jiho Chu wrote:
> It contains the base codes for trinity driver. Minimal codes to load and
> probe device is provided. The Trinity Family is controlled by the
> Memory-Mapped Registers, the register addresses and offsets are
> described. And user api interfaces are presented to control device under
> ioctl manner.
>
> + dev = &pdev->dev;
> + dev->id = ((desc->ver & TRINITY_MASK_DEV) >> TRINITY_SHIFT_DEV);
> +
> + /* set private data */
> + drv = devm_kzalloc(dev, sizeof(*drv), GFP_KERNEL);
> + if (drv == NULL)
> + return -ENOMEM;
> +
> + platform_set_drvdata(pdev, drv);
> + dev_set_drvdata(dev, drv);
> +
> + drv->dev = dev;
> + drv->desc = desc;
> +
> + np = dev->of_node;
> + if (of_property_match_string(np, "samsung,trinity-type", desc->type))
Let me be more specific.
You need to document your bindings.
Patch cannot be accepted without them.
Best regards,
Krzysztof
Powered by blists - more mailing lists