From: Michal Simek <michal.simek@amd.com>
To: Andrew Lunn <andrew@lunn.ch>, abdurrahman@nexthop.ai
Cc: Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] spi: xilinx: use device property accessors.
Date: Fri, 23 Jan 2026 08:11:47 +0100 [thread overview]
Message-ID: <ac0c9ceb-0c34-49f2-a486-1d87e488f607@amd.com> (raw)
In-Reply-To: <d6c5547b-0426-40d0-85b9-b64f183d37b6@lunn.ch>
On 1/22/26 17:18, Andrew Lunn wrote:
> On Thu, Jan 22, 2026 at 09:00:29AM +0000, Abdurrahman Hussain via B4 Relay wrote:
>> From: Abdurrahman Hussain <abdurrahman@nexthop.ai>
>>
>> Switch to device property accessors.
>>
>> Signed-off-by: Abdurrahman Hussain <abdurrahman@nexthop.ai>
>> ---
>> Switch to generic device property accessors.
>>
>> Changed from v3:
>>
>> Removed the patches to make irq optional from the series
>>
>> 2.52.0
>>
>> base-commit: 944aacb68baf7624ab8d277d0ebf07f025ca137c
>> ---
>> drivers/spi/spi-xilinx.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/spi/spi-xilinx.c b/drivers/spi/spi-xilinx.c
>> index c86dc56f38b4..c4b70e95b695 100644
>> --- a/drivers/spi/spi-xilinx.c
>> +++ b/drivers/spi/spi-xilinx.c
>> @@ -405,11 +405,11 @@ static int xilinx_spi_probe(struct platform_device *pdev)
>> bits_per_word = pdata->bits_per_word;
>> force_irq = pdata->force_irq;
>> } else {
>> - of_property_read_u32(pdev->dev.of_node, "xlnx,num-ss-bits",
>> - &num_cs);
>> - ret = of_property_read_u32(pdev->dev.of_node,
>> - "xlnx,num-transfer-bits",
>> - &bits_per_word);
>> + device_property_read_u32(&pdev->dev, "xlnx,num-ss-bits",
>> + &num_cs);
>> + ret = device_property_read_u32(&pdev->dev,
>> + "xlnx,num-transfer-bits",
>> + &bits_per_word);
>
> It could be my grep foo is broken, but there does not appear to be any
> users of xlnx,num-transfer-bits and xlnx,num-ss-bits. So it would be
> better to just remove them. There is no point Maintaining an API
> nobody uses. And it would be silly to spread that API to ACPI if
> nobody it going to use it.
>
"xlnx,num-transfer-bits"
bits_per_word is initializing bytes_per_word which is used in code for transfer
sizes calculations.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/spi/spi-xilinx.c?h=v6.19-rc6#n470
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/spi/spi-xilinx.c?h=v6.19-rc6#n125
"xlnx,num-ss-bits"
num_cs is used in host->num_chipselect to declare amount of chip selects.
Both are also the part of DT bindings. The name of property exactly match the
name used in design tool. That's why it is 1:1 mapping and driver is quite old
before num-cs property has been created.
Thanks,
Michal
next prev parent reply other threads:[~2026-01-23 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:00 Abdurrahman Hussain via B4 Relay
2026-01-22 16:18 ` Andrew Lunn
2026-01-23 7:11 ` Michal Simek [this message]
2026-01-23 12:40 ` Mark Brown
2026-01-23 14:14 ` Michal Simek
2026-01-23 14:16 ` Mark Brown
2026-02-04 12:01 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac0c9ceb-0c34-49f2-a486-1d87e488f607@amd.com \
--to=michal.simek@amd.com \
--cc=abdurrahman@nexthop.ai \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®