[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afae04e0-76a3-1bcb-5b47-9944fa9ab2c0@linaro.org>
Date: Fri, 22 Jul 2022 20:31:22 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tomer Maimon <tmaimon77@...il.com>, avifishman70@...il.com,
tali.perry1@...il.com, joel@....id.au, venture@...gle.com,
yuenn@...gle.com, benjaminfair@...gle.com, broonie@...nel.org,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org
Cc: openbmc@...ts.ozlabs.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 2/2] spi: npcm-pspi: Add NPCM845 peripheral SPI support
On 22/07/2022 13:41, Tomer Maimon wrote:
> Add Nuvoton BMC NPCM845 NPCM Peripheral SPI (PSPI) support.
>
> Signed-off-by: Tomer Maimon <tmaimon77@...il.com>
> ---
> drivers/spi/spi-npcm-pspi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/spi/spi-npcm-pspi.c b/drivers/spi/spi-npcm-pspi.c
> index 1668a347e003..7f2e4d1b0d43 100644
> --- a/drivers/spi/spi-npcm-pspi.c
> +++ b/drivers/spi/spi-npcm-pspi.c
> @@ -443,6 +443,7 @@ static int npcm_pspi_remove(struct platform_device *pdev)
>
> static const struct of_device_id npcm_pspi_match[] = {
> { .compatible = "nuvoton,npcm750-pspi", .data = NULL },
> + { .compatible = "nuvoton,npcm845-pspi", .data = NULL },
The devices look compatible, so why not reusing 750 compatible and
adding more specific upfront only in the bindings instead?
Best regards,
Krzysztof
Powered by blists - more mailing lists