[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5565351E.6050708@codeaurora.org>
Date: Tue, 26 May 2015 22:08:14 -0500
From: Timur Tabi <timur@...eaurora.org>
To: Hanjun Guo <hanjun.guo@...aro.org>, fu.wei@...aro.org,
Suravee.Suthikulpanit@....com, linaro-acpi@...ts.linaro.org,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
CC: tekkamanninja@...il.com, graeme.gregory@...aro.org,
al.stone@...aro.org, ashwin.chaugule@...aro.org, arnd@...db.de,
linux@...ck-us.net, vgandhi@...eaurora.org, wim@...ana.be,
jcm@...hat.com, leo.duran@....com, corbet@....net,
mark.rutland@....com, catalin.marinas@....com, will.deacon@....com
Subject: Re: [PATCH v3 6/6] ACPI: import watchdog info of GTDT into
platform device
Hanjun Guo wrote:
>> I don't agree with this. The GTDT should be parsed even if there's no
>> watchdog driver compiled for this kernel. There are no other #ifdefs in
>> this file.
>
> So what's the point of parse GTDT and alloc memories for it if there
> is no watchdog driver compiled for the kernel?
I don't think it's normal policy to generate a platform only if one
specific driver is enabled.
> will the module insmod
> later even if the CONFIG_ARM_SBSA_WATCHDOG=n?
I think that actually can work, but it's not a good reason by itself.
> OK, that's good point. but what I proposed is some hint to which driver
> will use the data prepared in this file, we can easily understand it
> in this patchset, but if just review the code in this fiel, I think
> people will be confused without detail comments.
All anyone needs to is
git grep "sbsa-gwdt"
And you'll find the driver.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists