From: Ninad Palsule <ninad@linux.vnet.ibm.com>
To: Andrew Lunn <andrew@lunn.ch>, Ninad Palsule <ninad@linux.ibm.com>
Cc: joel@jms.id.au, andrew@aj.id.au, eajames@linux.ibm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v1 1/1] soc/aspeed: Add host side BMC device driver
Date: Tue, 22 Aug 2023 11:14:15 -0500 [thread overview]
Message-ID: <6cea8ee7-f845-6ef3-631f-3f252ff5e949@linux.vnet.ibm.com> (raw)
In-Reply-To: <5159abb8-1b4c-4576-b370-4dd9db142beb@lunn.ch>
Hello Andrew,
Thanks for the review.
On 8/21/23 2:29 PM, Andrew Lunn wrote:
>> Testing:
>> - This is tested on IBM rainier system with BMC. It requires BMC side
>> BMC device driver which is available in the ASPEED's 5.15 SDK
>> kernel.
> How relevant is that? To the host side, it just appears to be an
> 16550A. Is the SDK emulating an 16550A? If you where to use a
> different kernel, is it still guaranteed to be an 16550A? I also
> notice there is a mainline
> drivers/tty/serial/8250/8250_aspeed_vuart.c. Could that be used on the
> BMC? That would be a better testing target than the vendor kernel.
This is just to indicate how I tested my code.
Yes, aspeed chip (in this case ast2600) is compatible with 16550 UART.
I am guessing it should work with different kernel too as 16550 standard
is used.
The 8250_aspeed_vuart.c is a BMC side driver for accessing VUART over
LPC bus and
this is a host side driver to access VUART over PCIe bus.
>> +config ASPEED_HOST_BMC_DEV
>> + bool "ASPEED SoC Host BMC device driver"
>> + default ARCH_ASPEED
>> + select SOC_BUS
>> + default ARCH_ASPEED
> same default twice?
Removed.
>
>> +static int __init aspeed_host_bmc_device_init(void)
>> +{
>> + int ret;
>> +
>> + /* register pci driver */
>> + ret = pci_register_driver(&aspeed_host_bmc_dev_driver);
>> + if (ret < 0) {
>> + pr_err("pci-driver: can't register pci driver\n");
>> + return ret;
>> + }
>> +
>> + return 0;
>> +
>> +}
>> +
>> +static void aspeed_host_bmc_device_exit(void)
>> +{
>> + /* unregister pci driver */
>> + pci_unregister_driver(&aspeed_host_bmc_dev_driver);
>> +}
>> +
>> +late_initcall(aspeed_host_bmc_device_init);
>> +module_exit(aspeed_host_bmc_device_exit);
> It looks like you can use module_pci_driver() ?
yes, It should work unless the late initcall is important. I will test
it and see.
Thanks & Regards,
Ninad Palsule
next prev parent reply other threads:[~2023-08-22 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 18:35 [PATCH v1 0/1] Host " Ninad Palsule
2023-08-21 18:35 ` [PATCH v1 1/1] soc/aspeed: Add host " Ninad Palsule
2023-08-21 19:29 ` Andrew Lunn
2023-08-22 16:14 ` Ninad Palsule [this message]
2023-08-23 17:32 ` Ninad Palsule
2024-01-11 16:23 ` Ninad Palsule
2023-08-23 7:57 ` kernel test robot
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=6cea8ee7-f845-6ef3-631f-3f252ff5e949@linux.vnet.ibm.com \
--to=ninad@linux.vnet.ibm.com \
--cc=andrew@aj.id.au \
--cc=andrew@lunn.ch \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ninad@linux.ibm.com \
/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®