On 11/12/2015 04:06 PM, Al Stone wrote:
On 11/05/2015 09:41 AM, Guenter Roeck wrote:
On 11/05/2015 07:00 AM, Fu Wei wrote:
Hi Timur,
On 5 November 2015 at 22:40, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote:
Fu Wei wrote:
Did you really read the "Note" above???????? OK, let me paste it again
and again:
SBSA 2.3 Page 23 :
If a larger watch period is required then the compare value can be
programmed directly into the compare value register.
Well, okay. Sorry, I should have read what you pasted more closely. But I
Thanks for reading it again.
think that means during initialization, not during the WS0 timeout.
I really don't see SBSA say "during initialization, not during the WS0 timeout",
please point it out the page number and the line number in SBSA spec.
maybe I miss it?
Thanks for your help in advance.
Anyway, I still don't like the fact that you're programming WCV in the
"you don't like" doesn't mean "it is wrong" or "we can't do this", so
I will keep this way unless we have better idea to extend second stage
timeout.
interrupt handler, but I'm not going to make a big deal about it any more.
Deal, Thanks a lot.
The problem with your driver, as I see it, is that dealing with WS0/WS1
and pretimeout makes the driver so complex that, at least for my part,
I am very wary about it. The driver could long since have been accepted
if it were not for that. Besides that, I really believe that any system designer
using the highest permitted frequency should be willing to live with the
consequences, and not force the implementation of a a complex driver.
Ultimately, you'll have to decide if you want a simple driver accepted, or
a complex driver hanging in the review queue forever.
Thanks,
Guenter
Sorry to poke my head in late like this, but I do have a vested interest in the
outcome so I'm very curious. For my work, I need to have an ACPI-supported,
SBSA-compliant watchdog timer for arm64, and this series is one of the key
pieces to getting there. The plan for me has been: (1) get an FDT based SBSA
watchdog timer, (2) add in kernel code to handle the ACPI GTDT table describing
timers, then (3) munge the SBSA watchdog timer for use by ACPI.
So, is this an actual NAK of the patch series as is? I think it is, but I want
it to be clear, and it has not been explicit yet.
I am not the maintainer, so I don't make the call. All I am saying is that I don't
feel comfortable with the code as is. Part of it is due to the the specification's
complexity, which leaves space for (mis)interpretations and bad implementations.
Either case, this is just my personal opinion. All you'll have to do is to convince
Wim to accept your patch.
If it is a NAK, that's fine, but I also want to be sure I understand what the
objections are. Based on my understanding of the discussion so far over the
multiple versions, I think the primary objection is that the use of pretimeout
makes this driver too complex, and indeed complex enough that there is some
concern that it could destabilize a running system. Do I have that right?
The other possible item I could conclude out of the discussion is that we do
not want to have the pretimeout code as part of the watchdog framework; is that
also the case or did I misunderstand?
Nothing really to do with pretimeout, but with the complexity of implementing it
for this driver.
As for pretimeout, it does have its issues. Some people say that hitting
a pretimeout should result in a panic, others just as strongly say that it
should just dump a message to the console. Which does make me a bit wary, since
it means that it may be implemented differently in different drivers, which
I consider highly undesirable.
And finally, a simpler, single stage timeout watchdog driver would be a
reasonable thing to accept, yes? I can see where that would make sense.
I am quite sure that such a driver would long since have been accepted.
The issue for me in that case is that the SBSA requires a two stage timeout,
Hmm - really ? This makes me want to step back a bit and re-read the specification
to understand where it says that, and what the reasoning might be for such a
requirement.
so a single stage driver has no real value for me. Now, if I can later add in
changes to make the driver into a two stage driver so it is SBSA-compliant,
that would also work, but it will make the driver more complex again. At that
point, I think I've now gone in a logical circle and the changes would not be
accepted so I could never get to my goal of an SBSA-compliant driver. I don't
think that's what was meant, so what did I miss?
Thanks in advance for any clarifications that can be provided.....I really do
appreciate it. Email is not always the clearest mechanism for communication
so sometimes I have to ask odd questions like these so I can understand what
is happening.
I don't really follow the logic here. Why ask if a single stage driver would
have been accepted just to point out that it would have no value for you ?
Really, just convince Wim to accept the driver.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
