[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230520165707.695de520@jic23-huawei>
Date: Sat, 20 May 2023 16:57:07 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Shreeya Patel <shreeya.patel@...labora.com>
Cc: lars@...afoo.de, heiko@...ech.de, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, sebastian.reichel@...labora.com,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...labora.com, gustavo.padovan@...labora.com,
serge.broslavsky@...labora.com, Simon Xue <xxm@...k-chips.com>
Subject: Re: [PATCH 1/7] iio: adc: rockchip_saradc: Add support for RK3588
On Wed, 17 May 2023 04:30:45 +0530
Shreeya Patel <shreeya.patel@...labora.com> wrote:
> Refactor conversion operation to support rk3588 saradc and
> add separate start, read, powerdown in respective hooks.
>
> Signed-off-by: Simon Xue <xxm@...k-chips.com>
> Signed-off-by: Shreeya Patel <shreeya.patel@...labora.com>
Hi Shreeya,
This particular chain of tags has unclear authorship.
If Simon wrote the driver, then the author (from address) of the
patch should be Simon's. If it is a codeveloped situation look
at how to use the co-developed-by tag
Generally the nicest way to add new callbacks is to do them in their
own patch. Then introduce new devices with different callbacks in a follow
on patch. That means the first one can be reviewed to ensure there
is no functional change separate from the new code in the following patch.
> +static const struct rockchip_saradc_data rk3588_saradc_data = {
> + .channels = rockchip_rk3588_saradc_iio_channels,
> + .num_channels = ARRAY_SIZE(rockchip_rk3588_saradc_iio_channels),
> + .clk_rate = 1000000,
> + .start = rockchip_saradc_start_v2,
As mentioned above, I'd like to see the changes for old devices done in patch
1 and the support for new device in a new patch.
> + .read = rockchip_saradc_read_v2,
> };
Powered by blists - more mailing lists