From: Guenter Roeck <linux@roeck-us.net>
To: Huang Rui <ray.huang@amd.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Denis Turischev <denis.turischev@compulab.co.il>,
Borislav Petkov <bp@alien8.de>, Vincent Wan <vincent.wan@amd.com>,
Tony Li <tony.li@amd.com>
Subject: Re: [PATCH 1/2] sp5100_tco: fix the device check for SB800 and later chipsets
Date: Tue, 24 Nov 2015 18:11:33 -0800 [thread overview]
Message-ID: <565518D5.4010104@roeck-us.net> (raw)
In-Reply-To: <20151125015916.GA2904@hr-amur2>
On 11/24/2015 05:59 PM, Huang Rui wrote:
> On Tue, Nov 24, 2015 at 05:58:03AM -0800, Guenter Roeck wrote:
>> On 11/23/2015 02:07 AM, Huang Rui wrote:
>>> For SB800 and later chipsets, the register definitions are the same
>>> with SB800. And for SB700 and older chipsets, the definitions should
>>> be same with SP5100/SB7x0.
>>>
>>> Signed-off-by: Huang Rui <ray.huang@amd.com>
>>> Cc: Denis Turischev <denis.turischev@compulab.co.il>
>>
>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>>
>> Would it make sense to rework this driver as pci driver ?
>>
>
> I agree with you. Actually, I thought about this stuff. But sp5100
> watchdog is not a pci device in AMD chipset. In another word, it
> doesn't export a pci header to OS. At current, we use SMBus pci device
> id and vendor id to detect watchdog on the AMD chipset (Because AMD
> use SMBus device id and revsion to identify different chipset
> version). At the same time, SMbus has its own driver piix4_smbus.
> Looks like we don't have a pci header to enumerate the watchdog.
>
Ok, thanks for the clarification. Odd way to detect the chip, but
I guess one has to use what is available.
Thanks,
Guenter
next prev parent reply other threads:[~2015-11-25 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 10:07 [PATCH 1/2] sp5100_tco: fix the device check for SB800 and later chipsets Huang Rui
2015-11-23 10:07 ` [PATCH 2/2] sp5100_tco: Add AMD Carrizo platform support Huang Rui
2015-11-24 14:00 ` Guenter Roeck
2015-12-27 19:46 ` Wim Van Sebroeck
2015-11-24 13:58 ` [PATCH 1/2] sp5100_tco: fix the device check for SB800 and later chipsets Guenter Roeck
2015-11-25 1:59 ` Huang Rui
2015-11-25 2:11 ` Guenter Roeck [this message]
2015-12-27 19:45 ` Wim Van Sebroeck
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=565518D5.4010104@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bp@alien8.de \
--cc=denis.turischev@compulab.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=tony.li@amd.com \
--cc=vincent.wan@amd.com \
--cc=wim@iguana.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.